Systems and methods for decryption as a service

ABSTRACT

Systems and methods for decryption of payloads are disclosed herein. In various embodiments, systems and methods herein are configured for decrypting thousands of transactions per second. Further, in particular embodiments, the systems and methods herein are scalable, such that many thousands of transactions can be processed per second upon replicating particular architectural components.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/900,286, filed Jun. 12, 2020, entitled “Systems and Methods forDecryption as a Service,” which is a continuation of Ser. No.15/923,382, filed Mar. 16, 2018, entitled “Systems and Methods forDecryption as a Service,” now U.S. Pat. No. 10,721,215, which is acontinuation of U.S. patent application Ser. No. 15/253,352, filed Aug.31, 2016, entitled “Systems and Methods for Decryption as a Service,”now U.S. Pat. No. 9,954,830, which is a continuation of U.S. patentapplication Ser. No. 14/663,238, filed Mar. 19, 2015, entitled “Systemsand Methods for Decryption as a Service,” now U.S. Pat. No. 9,461,973,which claims the benefit of and priority to U.S. Provisional PatentApplication No. 61/955,739, filed Mar. 19, 2014, entitled, “Systems andMethods of Point of Interaction Management,” and is acontinuation-in-part application of the following U.S. and international(PCT) applications:

U.S. patent application Ser. No. 14/591,223, filed Jan. 7, 2015,entitled “Systems and Methods for Creating Fingerprints of EncryptionDevices,” now U.S. Pat. No. 9,355,374;

U.S. patent application Ser. No. 14/591,171, filed Jan. 7, 2015,entitled “Systems and Methods for Facilitating Decryption of PayloadsReceived from Encryption Devices,”;

U.S. patent application Ser. No. 14/591,218, filed Jan. 7, 2015,entitled “Systems and Methods for Creating and Tracking States ofEncryption Devices,”; and International Patent Application No.PCT/US2015/010405, filed Jan. 7, 2015 entitled

“Systems and Methods for Creating Fingerprints of Encryption Devices;”

each of the above-referenced patents and patents applications are hereinincorporated by reference in their entireties.

TECHNICAL FIELD

The present disclosure relates generally point to point encryption(P2PE) and management of point to point encryption systems.

BACKGROUND

Protecting cardholder data during an electronic payment transaction isvital for all entities involved in the processing of that transaction.It was recently made public that in the fourth quarter of 2013 andthroughout 2014, significant data breaches occurred at major nationalretailers. In each instance, cardholder account numbers, and associatedcardholder personal data, were illegally obtained by maliciousfraudsters, exposing millions of sensitive payment records to potentialfraudulent use, including identity theft. As a result, each retailerexperienced damages in terms of lost sales, fines, and potentiallawsuits for alleged negligence with regard to payment securitystandards. Another serious consequence of such breaches is branderosion.

Data breaches are not a new occurrence in the payments industry, but theincreasing number of breaches that occur each year, their severity interms of numbers of records obtained, and the speed and stealth withwhich such breaches occur is new.

It is not a matter of if a business will experience a breach, it's amatter of when. While it is impossible to eliminate the possibility of adata breach occurring, it is now possible to protect cardholder dataintegrity in the event of a breach through PCI-validated point-to-pointencryption (P2PE). PCI-validated P2PE renders any potential cardholderdata useless and void of value in the event of a data theft because thecardholder data cannot be decrypted.

BRIEF SUMMARY OF THE DISCLOSURE

In various embodiments, the systems and methods herein include a pointto point encryption management system configured to receive informationfrom a plurality of point of interaction devices, the point to pointencryption management system including a) a database for storing deviceinformation and b) at least one processor operatively coupled to thedatabase, the at least one processor configured for: 1) receiving apayload originating from a point of interaction device, the payloadincluding encrypted payment information and a device identifier; 2)parsing the payload to extract the device identifier; 3) retrieving anidentifier table from the database, the identifier table including oneor more device identifiers received by the point to point encryptionmanagement system; 4) comparing the device identifier to the identifiertable to determine whether the device identifier is included in theidentifier table; and 5) upon determining that the device identifier isincluded in the identifier table, facilitating decryption of theencrypted payment information.

According to particular embodiments, the systems and methods hereininclude a point to point encryption management system configured toreceive information from a plurality of point of interaction devices,the point to point encryption management system including a) a databasefor storing device information and b) at least one processor operativelycoupled to the database, the at least one processor configured for: 1)receiving a payload originating from a point of interaction device, thepayload including encrypted data and a device serial number; 2) parsingthe payload to extract the device serial number; 3) retrieving a serialnumber table from the database, the serial number table including one ormore serial numbers received by the point to point encryption managementsystem; 4) comparing the device serial number to the serial number tableto determine whether the device serial number is included in the serialnumber table; 5) upon determining that the device serial number isincluded in the table, retrieving, from memory, a fingerprint associatedwith a record of the point of interaction device, wherein thefingerprint is an identifier created by the point to point encryptionmanagement system for the point of interaction device based on theformat of one or more payloads that originated from the point ofinteraction device; 6) comparing the payload to the fingerprint todetermine whether the point of interaction device has been compromised;and 7) upon determining that the point of interaction device has notbeen compromised, facilitating decryption of the encrypted payment cardinformation.

In one or more embodiments, the systems and methods herein include acomputer-implemented method for decrypting encrypted data, thecomputer-implemented method including: A) providing at least oneencryption device including at least one processor configured totransmit encrypted data and a device serial number; and B) providing anencryption management system configured to receive information from theencryption device and at least one computer terminal located at a keyinjection facility, the encryption management system including a) adatabase for storing device information and b) at least one processoroperatively coupled to the database, the at least one processorconfigured for: 1) receiving an initial device serial number from the atleast one terminal located at the key injection facility; 2) writing theinitial device serial number to a table in memory and storing the tablein a database; 3) receiving a payload at least partially originatingfrom the encryption device, the payload including encrypted data and thedevice serial number; 4) parsing the payload to extract the deviceserial number; 5) retrieving the table from the database; 6) comparingthe device serial number to the initial device serial number todetermine whether the device serial number is included in the table; and7) upon determining that the device serial number and the initial deviceserial number are the same serial number, facilitating decryption of theencrypted data.

According to some embodiments, the systems and methods herein include acomputer system for point to point encryption of payment transactions,the computer system including: A) at least one point of interactiondevice including a) one or more magnetic read heads for reading consumerpayment cards and b) at least one processor configured to transmitconsumer payment card information and a device serial number associatedwith the at least one point of interaction device; B) a hardwaresecurity module configured for decryption of payment card information;and C) a point to point encryption management system configured toreceive information from the point of interaction device and at leastone computer terminal located at a key injection facility, the point topoint encryption management system including a) a database for storingdevice information and b) at least one processor operatively coupled tothe database, the at least one processor configured for: 1) receiving aninitial device serial number from the at least one computer terminallocated at the key injection facility; 2) writing the initial deviceserial number to a table in memory and storing the table in thedatabase; 3) receiving a first payload originating from the point ofinteraction device, the first payload including first encrypted paymentcard information and the device serial number; 4) parsing the payload toextract the device serial number; 5) retrieving the table from thedatabase; 6) comparing the device serial number to the initial deviceserial number to determine whether the device serial number is includedin the table; 7) upon determining that the device serial number and theinitial device serial number are the same serial number: i) facilitatingdecryption of the payment card information; and ii) creating afingerprint for the point of interaction device based on the format ofthe first payload and storing the payload identifier in memory; 8)receiving a second payload originating from the point of interactiondevice including encrypted second payment card information and thedevice serial number; 9) parsing the received second payload to extractthe device serial number; 10) retrieving the table from the database;11) comparing the device serial number to the initial device serialnumber to determine whether the device serial number is included in thetable; 12) upon determining that the device serial number and theinitial device serial number are the same serial number, retrieving thefingerprint; 13) comparing the second payload to the fingerprint todetermine whether the point of interaction device has been compromised;and 14) upon determining that the point of interaction device has notbeen compromised, transmitting the second payment information to thehardware security module for decryption.

In at least one embodiment, the systems and methods herein include acomputer system decrypting payment transactions, the computer systemincluding: A) at least one point of interaction device including one ormore processors configured to transmit consumer payment card informationand a device serial number associated with the at least one point ofinteraction device; and B) a point to point encryption management systemconfigured to receive information from the point of interaction deviceand at least one computer terminal located at a key injection facility,the point to point encryption management system including a) a databasefor storing device information and b) at least one processor operativelycoupled to the database, the at least one processor configured for: 1)receiving an initial device serial number from the at least one computerterminal located at the key injection facility; 2) writing the initialdevice serial number to a table in memory and storing the table in thedatabase; 3) receiving a payload at least partially originating from thepoint of interaction device, the payload including encrypted paymentcard information and the device serial number; 4) parsing the payload toextract the device serial number; 5) retrieving the table from thedatabase; 6) comparing the device serial number to the initial deviceserial number to determine whether the device serial number is includedin the table; and 7) upon determining that the device serial number andthe initial device serial number are the same serial number,facilitating decryption of the payment card information.

In further embodiments, the systems and methods herein include acomputer-implemented method for decrypting payment transactions, themethod including: 1) providing at least one point of interaction deviceincluding one or more processors configured to transmit consumer paymentinformation and a device serial number associated with the at least onepoint of interaction device; 2) providing a point to point encryptionmanagement system configured to receive information from the point ofinteraction device, the point to point encryption management systemincluding a) a database for storing device information and b) at leastone processor operatively coupled to the database; 3) receiving, by theleast one processor, an initial device serial number at least onecomputer third party computing device; 4) writing, by the least oneprocessor, the initial device serial number to a table in memory andstoring the table in the database; 5) receiving, by the at least oneprocessor, a payload at least partially originating from the point ofinteraction device, the payload including encrypted payment informationand the device serial number; 6) parsing, by the at least one processor,the payload to extract the device serial number; 7) comparing, by the atleast one processor, the device serial number to the initial deviceserial number to determine whether the device serial number and theinitial serial number are the same serial number; and 8) upondetermining that the device serial number and the initial device serialnumber are the same serial number, facilitating decryption of thepayment information.

According to various embodiments, the systems and methods herein includea computer system for creating a fingerprint for a device, the computersystem including the device operatively connected to a device managementsystem, the device management system including at least one processoroperatively coupled to at least one database, the at least one processorconfigured for: 1) receiving a first payload from the device, the firstpayload including data in a particular format and a device indicator,the device indicator including a unique identifier used for identifyingthe device; 2) creating the fingerprint for the device, the fingerprintincluding a section format for each of one or more distinct sections ofthe particular format in a particular order; 3) storing a record of thefingerprint for the device and the unique identifier at the at least onedatabase; and 4) comparing a format of each subsequent payload receivedfrom the device to the fingerprint for the device to determine whetherthe device has been compromised.

In particular embodiments, the systems and methods herein include acomputer system for creating a fingerprint for a device, the computersystem including the device operatively connected to a device managementsystem, the device management system including at least one processoroperatively coupled to at least one database, the at least one processorconfigured for: 1) receiving payloads from a particular device, eachpayload including encrypted and unencrypted data in a format; 2)comparing the format of each payload from the particular device to thefingerprint associated with the particular device; and 3) upondetermining that the format of a particular payload of the payloadsreceived from the particular device does not match the fingerprintassociated with the particular device, declining to decrypt theencrypted data of the particular payload and transmitting a notificationof declining to decrypt the encrypted data to a user computing systemassociated with a user.

According to one or more embodiments, the systems and methods hereininclude a computer-implemented method for creating a fingerprint for adevice, the method including: A) providing a device capable ofencrypting data; B) providing a computer system operatively coupled tothe device, the computer system including: 1) a decrypting means fordecrypting data received from the device; 2) a fingerprint creationmeans for creating a fingerprint associated with the device; 3) at leastone database; and 4) at least one processor operatively coupled to thedecrypting means, the fingerprint creation means, and the at least onedatabase; C) receiving, by the at least one processor, a first payloadfrom the device, the first payload including data in a particularformat, a device indicator, and encrypted data, the device indicatorincluding a unique identifier used for identifying the device; D)creating, by the fingerprint creation means, a fingerprint for thedevice, the fingerprint including a section format for each of one ormore distinct sections of the particular format in a particular order;E) storing a record of the fingerprint for the device and the uniqueidentifier at the at least one database and changing a state of thedevice to active by the at least one processor; F) comparing, by the atleast one processor, a second particular format of a subsequent payloadreceived from the device to the fingerprint for the device to determinewhether the device has been compromised; and G) upon determining thatthe device has not been compromised, decrypting, by the decryptingmeans, encrypted data of the subsequent payload.

In at least one particular embodiment, the systems and methods hereininclude computer system for managing encryption device status changesincluding a P2PE management system including at least one processor andoperatively connected to an encryption device, the at least oneprocessor configured for changing a state of the encryption device basedupon transactional information received from the encryption device,wherein changing the state of the encryption device based upontransaction information includes: 1) receiving a transaction payloadfrom an encryption device, the transaction payload including transactioninformation and non-transaction information; 2) determining whether thetransaction information is unencrypted; and 3) in response todetermining that the transaction information is unencrypted, disablingthe encryption device by changing a state of the encryption device to atampered state.

In further embodiments, the systems and methods herein include acomputer-implemented method for managing encryption device statuschanges, the method including the steps of: A) providing a P2PEmanagement system including at least one processor and operativelyconnected to an encryption device; and B) changing, by the at least oneprocessor, a state of the encryption device based upon transactionalinformation received from the encryption device, wherein changing thestate of the encryption device based upon transaction informationincludes: 1) receiving a transaction payload from an encryption device,the transaction payload including transaction information andnon-transaction information; 2) determining whether the transactioninformation is unencrypted; and 3) in response to determining that thetransaction information is unencrypted, disabling the encryption deviceby changing a state of the encryption device to a tampered state.

In still further embodiments, the systems and methods herein include acomputer system for managing encryption device status changes includinga P2PE management system including at least one processor andoperatively connected to an encryption device, the at least oneprocessor configured for: A) changing the state of the encryption devicebased on input from an operator; B) changing a state of the encryptiondevice based upon transactional information received from the encryptiondevice, wherein changing the state of the encryption device based upontransaction information includes: 1) receiving a first transactionpayload from an encryption device, the first transaction payloadincluding first transaction information and first non-transactioninformation; 2) upon receiving the first transaction payload from theencryption device, changing the state of the encryption device from thedeployed state to an active state and facilitating decryption of thefirst transaction information; 3) receiving a second transaction payloadfrom the encryption device, the second transaction payload includingsecond transaction information and second non-transaction information;4) determining whether the second transaction information isunencrypted; and 5) in response to determining that the secondtransaction information is unencrypted, disabling the encryption deviceby changing the state of the encryption device from the active state toa tampered state.

According to particular embodiments, the systems and methods hereininclude a system for decryption of payloads, the system comprising: afrontend server operatively connected to a read-only database, thefrontend server configured for: a) receiving a plurality of payloadsfrom one or more third parties, wherein each of the payloads includes atleast one encrypted element; b) retrieving authentication data from theread-only database; c) comparing the authentication data with each ofthe plurality of payloads to determine whether one or more of thepayloads of the plurality of payloads has been compromised; d) upondetermining that one or more of the payloads of the plurality ofpayloads has not been compromised, transmitting the one or more payloadsof the plurality of payloads to a hardware security module fordecryption of the at least one encrypted element; the read-only databaseoperatively connected to the frontend server and configured for storingread-only authentication data for use in determining whether payloadshave been compromised; and the hardware security module operativelyconnected to the frontend server, the hardware security moduleconfigured for decrypting the one or more payloads of the plurality ofencrypted payloads based on an encryption key and transmitting thedecrypted one or more payloads to the one or more third parties.

In one or more embodiments, the systems and methods herein include acomputer-implemented method for decryption of payloads, the methodcomprising: providing a frontend server operatively connected to aread-only database, the frontend server configured for: a) receiving aplurality of payloads from one or more third parties, wherein each ofthe payloads includes at least one encrypted element; b) retrievingauthentication data from the read-only database; c) comparing theauthentication data with each of the plurality of payloads to determinewhether one or more of the payloads of the plurality of payloads hasbeen compromised; d) upon determining that one or more of the payloadsof the plurality of payloads has not been compromised, transmitting theone or more payloads of the plurality of payloads to a hardware securitymodule for decryption of the at least one encrypted element; providingthe read-only database operatively connected to the frontend server andconfigured for storing read-only authentication data for use indetermining whether payloads have been compromised; and providing thehardware security module operatively connected to the frontend server,the hardware security module configured for decrypting the one or morepayloads of the plurality of encrypted payloads based on an encryptionkey and transmitting the decrypted one or more payloads to the one ormore third parties.

According to some embodiments, the systems and methods herein include ascalable system for fast decryption of payloads, the system comprising:at least one hardware security module operatively connected to one ormore frontend servers and configured for decrypting encrypted elementsof payloads; the one or more frontend servers configured to receive andauthenticate payloads based at least in part upon retrievingauthentication data from a particular read-only database of one or moreread-only databases; the one or more read-only databases operativelyconnected to the one or more frontend servers, wherein the one or moreread-only databases comprise the authentication data for authenticatingpayloads; a read-only master database operatively connected to the oneor more read-only databases, the read-only master database configured torefresh the authentication data stored at the one or more read-onlydatabases; and a backend read/write database for logging decryptions andauthentications, the backend read/write database operatively connectedto the at least one hardware security module and the read-only masterdatabase.

In at least one embodiment, the systems and methods herein include asystem for fast decryption of one or more payloads, the systemcomprising a message queuing protocol operatively connected to aread-only database and a read/write database, the message queuingprotocol configured for: receiving event notifications from a read-onlydatabase, wherein the event notifications each comprise one or morenotifications regarding the authentication of one or more receivedpayloads; queuing the event notifications received from the read-onlydatabase; and transmitting the event notifications to the read/writedatabase upon determining that the read/write database is configured toaccept event notifications.

In further embodiments, the systems and methods herein include acomputer-implemented method for fast decryption of one or more payloads,the method comprising providing a message queuing protocol operativelyconnected to a read-only database and a read/write database, the messagequeuing protocol configured for: receiving event notifications from aread-only database, wherein the event notifications each comprise one ormore notifications regarding the authentication of one or more receivedpayloads; queuing the event notifications received from the read-onlydatabase; and transmitting the event notifications to the read/writedatabase upon determining that the read/write database is configured toaccept event notifications.

According to various embodiments, the systems and methods herein includea system for fast decryption of one or more payloads, the systemcomprising: a frontend server for receiving encrypted payloads; aplurality of read-only databases operatively connected to the frontendserver; a master read-only database operatively connected to each of theplurality of read-only databases; and a read/write database operativelyconnected to the master database, the read/write database fortransmitting event messages to the master read-only database, whereinthe system is configured for: receiving event information at theread/write database; upon receiving the event information at theread/write database, automatically transmitting authentication data tothe master read-only database, wherein the authentication data has beenupdated by the event information; refreshing the read-only masterdatabase to include the authentication data; and refreshing each of theplurality of read-only databases with authentication data matching therefreshed read-only master database, wherein the authentication data isfor determining whether a payload has been transmitted by a tampereddevice.

In particular embodiments, the systems and methods herein include acomputer-implemented method for fast decryption of one or more payloads,the method comprising the steps of: providing a frontend server forreceiving encrypted payloads; providing a plurality of read-onlydatabases operatively connected to the frontend server; providing amaster read-only database operatively connected to each of the pluralityof read-only databases; providing a read/write database operativelyconnected to the master database, the read/write database fortransmitting event messages to the master read-only database; receivingevent information at the read/write database; upon receiving the eventinformation at the read/write database, automatically transmittingauthentication data to the master read-only database, wherein theauthentication data has been updated by the event information;refreshing the read-only master database to include the authenticationdata; and refreshing each of the plurality of read-only databases withauthentication data matching the refreshed read-only master database,wherein the authentication data is for determining whether a payload hasbeen transmitted by a tampered device.

According to one or more embodiments, the systems and methods hereininclude a system for decryption of one or more payloads, the systemcomprising: a hardware security module for decrypting encrypted elementsof received payloads, the hardware security module operatively connectedto at least one decryption server; the at least one decryption server,wherein the at least one decryption server is configured to: receive aparticular payload, the particular payload comprising at least oneencrypted element; transmit the particular payload to the hardwaresecurity module for decryption of the at least one encrypted element;upon receiving the particular payload from the hardware security module,parse the particular payload to determine whether the at least oneencrypted element has been decrypted by the hardware security module;upon determining that the at least one encrypted element has not beendecrypted by the hardware security module, transmit an error message toa read/write database operatively coupled to the frontend server.

In at least one particular embodiment, the systems and methods hereininclude a computer-implemented method for decryption of one or morepayloads, the method comprising: providing a hardware security modulefor decrypting encrypted elements of received payloads, the hardwaresecurity module operatively connected to at least one decryption server;providing the at least one decryption server; receiving a particularpayload, the particular payload comprising at least one encryptedelement; transmitting the particular payload to the hardware securitymodule for decryption of the at least one encrypted element; uponreceiving the particular payload from the hardware security module,parsing the particular payload to determine whether the at least oneencrypted element has been decrypted by the hardware security module;and upon determining that the at least one encrypted element has notbeen decrypted by the hardware security module, transmitting an errormessage to a read/write database operatively coupled to the frontendserver.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings illustrate one or more embodiments and/oraspects of the disclosure and, together with the written description,serve to explain the principles of the disclosure. A number of thediagrams below are unified modeling language (UML) 2.5 SequenceDiagrams. UML sequence diagrams focus on the message interchange betweenthe numbers of lifelines (aka individual participants). One of ordinaryskill in the art will understand that UML diagrams are read from left toright and from the top to the bottom. Seewww.uml-diagrams.org/sequence-diagrams-combined-fragment.html for moreinformation on UML diagrams.

FIG. 1 is an exemplary point to point encryption (P2PE) managementsystem and payments environment according to one embodiment of thepresent systems and methods.

FIG. 2A shows a block diagram of an exemplary architecture of the P2PEmanagement system and payments environment of FIG. 1 according to oneembodiment of the present systems and methods.

FIG. 2B shows a block diagram of an exemplary architecture of the P2PEmanagement system of FIG. 2A according to one embodiment of the presentsystems and methods.

FIG. 2C shows a block diagram of an alternate exemplary architecture ofthe P2PE management system of FIG. 2A according to one embodiment of thepresent systems and methods.

FIG. 3 is a flow chart illustrating an exemplary point of interactionmanagement process according to one embodiment of the present systemsand methods.

FIG. 4A is a flow chart illustrating an exemplary merchant data processaccording to one embodiments of the present systems and methods.

FIG. 4B is a flow charts illustrating an exemplary P2PE report processesaccording to one embodiment of the present systems and methods.

FIG. 5A is a flow chart illustrating an exemplary decryption processaccording to one embodiment of the present systems and methods.

FIG. 5B is a flow chart illustrating an exemplary fingerprint processaccording to one embodiment of the present systems and methods.

FIGS. 6-14 are UML diagrams illustrating exemplary sequences of thepresent systems and methods.

FIG. 15 is a flow chart illustrating an exemplary queuing processaccording to one embodiment of the present systems and methods.

FIG. 16 is a flow chart illustrating an exemplary update processaccording to one embodiment of the present systems and methods.

FIG. 17 is a flow chart illustrating an exemplary decryptionverification process according to one embodiment of the present systemsand methods.

DETAILED DESCRIPTION

For the purpose of promoting an understanding of the principles of thepresent disclosure, reference will now be made to the embodimentsillustrated in the figures and specific language will be used todescribe the same. It will, nevertheless, be understood that nolimitation of the scope of the disclosure is thereby intended; anyalterations and further modifications of the described or illustratedembodiments, and any further applications of the principles of thedisclosure as illustrated therein are contemplated as would normallyoccur to one skilled in the art to which the disclosure relates.

Prior to a detailed description of the disclosure, the followingdefinitions are provided as an aid to understanding the subject matterand terminology of aspects of the present systems and methods, areexemplary, and not necessarily limiting of the aspects of the systemsand methods, which are expressed in the claims. Whether or not a term iscapitalized is not considered definitive or limiting of the meaning of aterm. As used in this document, a capitalized term shall have the samemeaning as an uncapitalized term, unless the context of the usagespecifically indicates that a more restrictive meaning for thecapitalized term is intended. However, the capitalization or lackthereof within the remainder of this document is not intended to benecessarily limiting unless the context clearly indicates that suchlimitation is intended.

Definitions/Glossary

Account Data: may refer to cardholder data and/or sensitiveauthentication data, such as, but not limited to a PAN, a routingnumber, a cardholder name, an expiration date, a service code, magneticstripe data (or chip data), a card security code (e.g., CAV2, CVC2,CVV2, CID, etc.), one or more personal identification (PIN) numbers,and/or PIN blocks.

Bank: any suitable banking entity that may issue one or more cards(e.g., credit cards, debit cards, etc.) to a consumer, may receivedeposits (e.g., from a merchant), manage accounts for customers, etc.

Fingerprint or Device Fingerprint: in various embodiments, a set ofinformation used to identify a particular device, wherein the set ofinformation may be based on the particular device's one or moreattributes. In at least one embodiment, the set of information is for aPOI Device and includes a serial number associated with the POI Device.

Hardware Security Module (HSM): a device that, in various embodiments,safeguards, houses, and manages digital encryption and decryption keys.

Key Injection Facility (KIF): a secure service facility that injectsencryption keys (e.g., symmetric or asymmetric keys) into a device,typically a POI Device. The injected encryption key is used, inparticular embodiments, to encrypt data (e.g., consumer data, such asPAN data) received by the POI Device.

Merchant: an entity that provides or sells goods and/or services toconsumers and, in various embodiments, purchases, orders, and/or employsone or more POI Devices and utilizes the P2PE Manager.

P2PE Manager: in various embodiments, an application, software,hardware, and/or virtual machines for managing various state changes ofa POI Device, for reporting state changes of a POI Device (or POIDevices), for determining decryption key index names, for authenticatingthird party partners and devices, and/or for providing reports forMerchants for compliance or other purposes.

P2PE Payload, Transaction Payload, or Payload: a bundle of informationtransmitted from a POI Device. A payload may include any variety ofsuitable information. As a non-limiting example, in particularembodiments, a payload includes consumer information, such as a card'sPAN as well as a POI Device serial number. In various embodiments, apayload is sent to the P2PE Manager. In at least one embodiment, apayload is transmitted to a Payment Processor/Payment Network beforedecryption.

Payment Card Industry (PCI): generally, the debit, credit, prepaid,e-purse, e-wallet, ATM, and point of sale card industry and associatedbusinesses.

Payment Processor/Payment Network: one or more entities (typically athird party) that processes payments (e.g., credit card transactions)for a Merchant.

PCI Security Council: a council originally formed by American Express,Discover Financial Services, JCB, MasterCard Worldwide, and VisaInternational for managing the PCI Data Security Standard. By meetingvarious PCI Security Council requirements, businesses can be deemed “PCICompliant” or “PCI Validated.”

PCI Validation/Validated (PCI Compliant): an entity may be deemed PCIValidated by meeting various criteria set forth by the PCI SecurityCouncil. PCI Validated companies and/or solutions may be listed by thePCI Security Council (e.g., on the PCI Security Council website or inother suitable locations).

Point of Interaction (POI) Device (Point of Entry Device): in variousembodiments, a component of a point of sale system that enables aconsumer to make a purchase at a Merchant, such as with a payment card.POI Devices may or may not be consumer-facing and may require a PINnumber and/or other authentication. Non-limiting examples of POI Devicesinclude magnetic card readers (e.g., for reading a payment card, such asa credit card) and near field communication (NFC) devices (e.g., forreceiving a consumer's payment information from an electronic device,such as a mobile device). POI Devices may or may not be PCI Councilapproved devices.

Point to Point Encryption (P2PE): a combination of secure devices,applications, and processes that encrypt data from the point ofinteraction (for example, at the point of swipe) until the data reachesthe solution provider's secure decryption environment.

Primary Account Number (PAN): an account number typically found on thefront side of a payment card (e.g., a credit card number).

State(s): a recordable state and/or status of a particular device suchas a POI Device. Various states and/or statuses may include “new,”“active,” “lost,” “stolen,” “tampered,” “damaged,” “malfunction,”“quarantined,” “in repair,” “retired,” and “destroyed.”

State Changes: a recordable change in the state of a device, such as aPOI Device. In a particular example, a POI Device state may be changedfrom “active” to “lost” based on various factors.

Overview

The present systems and methods relate generally to management ofencryption processes, management of encryption devices, validationhandling of encryption devices (including point-to-point encryptiondevices), and managing, assigning, and reporting state changes ofencryption devices. According to particular embodiments, the presentsystems and methods track handling of decryption devices and theirrespective payloads (e.g., outputs of swipe data, etc.). It should beunderstood from the disclosure herein that the management of theencryption processes described herein may be, in some embodiments, PCIvalidated and compliant.

According to particular embodiments, the systems and methods herein aredirected to secure encryption device handling. Particularly, the systemsand methods herein are directed to: 1) receiving an indication of astate of a particular device; 2) receiving a payload from the particulardevice, including a device serial number and encrypted payload; 3)creating a record (e.g., a fingerprint) of the format of the payload andstoring the record in memory; 4) receiving a second payload from theparticular device, the second payload including the device serial numberand a second encrypted payload; 5) retrieving the record of the formatof the payload associated with the particular device from memory; 6)comparing the record of format of the payload to the format of thesecond payload; and 7) upon determining that that the format of thesecond payload does not match the record of the record of format of thepayload, changing the state of the particular device to a tamperedstate.

In one or more aspects, the systems and methods herein are directed tofacilitating decryption of encryption device payloads based on a deviceserial number included in the payload. In these aspects (and others),the system is configured to retrieve various information regarding theparticular device from a database based on the device serial number.Such data may include, for example, a record of the format of a firstpayload of the particular device (as discussed above), a key indexnumber indicating a base key used as the basis for encrypting a payloadof the particular device, a state of the particular device, etc.

According to various aspects, the systems and methods herein are furtherdirected to create a “fingerprint” of a particular device. Particularly,the system may be configured to create a fingerprint of the particulardevice to be used as a comparison to payloads received from theparticular device to determine whether the particular device iscompromised (e.g., the device has been stolen, hacked, etc.). The systemmay be configured to create the fingerprint of the particular device inany suitable way such as, for example, by parsing a first payloadreceived from the particular device, determining the format of eachsegment of the first payload, recording the format of each segment ofthe first payload in an order of the payload.

In some aspects, the systems and methods herein are directed to creatingreports regarding states and locations of encryption devices tracked bythe system. In these aspects, the system is configured to receive areport request from a merchant, compile the report based on stateinformation associated with encryption devices associated with themerchant, request that the merchant attest to the information includedin the report, and provide the report to the merchant.

As will be understood by one of ordinary skill in the art, the systemsand methods herein may be used by any suitable entity. Further, thesystems and methods described herein may be utilized for any suitableencryption/decryption process, including, but not limited to,point-to-point encryption, encryption/decryption of medical data,encryption/decryption of social security numbers, etc. The followingexemplary functionality of the systems and methods herein is includedfor the purpose of furthering understanding of the included systems andmethods and is intended to be exemplary and non-limiting.

Exemplary P2PE Manager and Payments Functionality Turing now to thefigures, FIG. 1 depicts a high-level exemplary P2PE manager and paymentsenvironment and process. In general, FIG. 1 shows an exemplary path ofan exemplary point of interaction (POI) device from a manufacturer(e.g., manufacturer 102) to a merchant (e.g., merchant 132) and thevarious processes and state changes associated with the exemplary POIdevice. FIG. 1 further depicts data received by the P2PE system 160,exemplary high level of data processing that occurs at the P2PE system,and an exemplary payment cycle.

FIG. 1 shows an exemplary P2PE manager and process wherein swipe (aswill be understood by one of ordinary skill in the art, data may also bekeyed into a user interface) data is sent from a merchant swipe terminal(e.g., a POI device) to a payment network, then to the P2PE system.

FIG. 1 depicts a manufacturer 102 of point of interaction (POI) devices(e.g., POI device 104). According to particular embodiments,manufacturer 102 produces POI device 104 in response to receiving apurchase order from a merchant or from a P2PE system (e.g., P2PE system160). In various embodiments, manufacturer 102 produces POI device 104(and any other POI devices) in any suitable way, as will be understoodby one of ordinary skill in the art. In particular embodiments,manufacturer 102 produces POI devices designed to output a device serialnumber and information in a particular format, as will be furtherdiscussed herein.

POI device 104 may be any device suitable of receiving information froma consumer. In various embodiments, POI device 104 receives paymentinformation, as discussed throughout this document, although it shouldbe understood by one of ordinary skill in the art that POI device 104should not be considered limited to only payment information.

POI device 104 may include any suitable components for receiving paymentinformation (e.g., credit card magnetic strip information, paymentinformation received from a mobile device, such as a smartphone, tablet,PDA, etc., chip information (e.g., from cards with embedded chips),payment information received from a check-out station, other sensitiveinformation, such as medical records received from an electronic medicalrecords system, etc.). In various embodiments, POI device 104 readsand/or receives payment information via a magnetic card reader forreading a card's magnetic strip (e.g., a credit card). In one or moreembodiments, POI device 104 includes a pin-pad, biometric scanner (e.g.,finger print or retina scanner), and/or chip reader for receivingsecondary consumer identity-verification information. In at least oneembodiment, POI device 104 is configured for receiving paymentinformation via one or more radios, such as a near-field communicationsradio, a suitable wireless network connection radio, such as aBluetooth, Bluetooth Low Energy (BLE), and/or Wi-Fi radio (e.g., POIdevice may receive payment information from an application (mobilewallet) included on mobile device via a “tap”).

As will be further discussed herein, POI device 104 transmitsinformation received from a consumer (e.g., payment information,biometric information, PIN information, etc.) to another system/devicefor processing. In various embodiments, POI device 104 is configured toencrypt received information upon receipt of said information. Accordingto particular embodiments, POI device 104 transmits information receivedfrom the consumer with device information, such as a serial numberassociated with POI device 104 for identification of the POI device. Insome embodiments, POI device 104 is configured to transmit theinformation received from the consumer and device information in aparticular format, which may be used by a P2PE system (e.g., P2PE system160) to form a “fingerprint” (e.g., an identifier based on the formatand/or device information of POI device 104) for identifyingtransactions sent from POI device 104.

As will be understood by one of ordinary skill in the art, POI device104 may be any POI device approved by the PCI Security Standards Council(“PCI SSC”) or other suitable device for receiving information to beencrypted. Examples of PCI SSC-approved devices can be found on PCISSC's website athttps://www.pcisecuritystandards.org/approved_companies_providers/approved_pin_transaction_security.php.In one or more embodiments, POI device 104 is a stand-alone swipeterminal, such as ID TECH's SecuRED™ SRED device. In some embodiments,POI device 104 is an all in one type mobile business solution, such as4P Mobile Data Processing's FDA600-POS device. In at least oneembodiment, the POI device 104 is a countertop terminal, such as AtosWorldline's Yomani device.

Still referring to FIG. 1, manufacturer 102 ships POI device 104 viasecure shipping 106 to a key injection facility (KIF) 110. As will beunderstood by one of ordinary skill in the art, secure shipping 106 mayrepresent any suitable type of secure shipping known in the art,including, but not limited to, via FedEx, UPS, etc. and/or by shippingvia air, ground, rail, etc.

Once received by KIF 110, in one or more embodiments, informationregarding POI device 104 is entered into P2PE manager 166. In variousembodiments, the information regarding POI device 104 includes a deviceserial number (e.g., to be matched later to swipe transactions). In atleast one embodiment, the information regarding POI device 104 includesa firmware version number. In further embodiments, the informationregarding POI device 104 includes a date of manufacture, the name of themanufacturer (e.g., manufacturer 102), etc.

Information regarding POI device 104 may be entered into the P2PEmanager 166 in any suitable way, such as, for example, by user interface180 or via an API interface. In various embodiments, a KIF employeescans in a serial number associated with POI device 104 via a suitablescanning mechanism (e.g., a hand-held barcode scanner or the like). Insome embodiments, a KIF employee keys in a serial number associated withPOI device 104 via a keyboard (or other suitable key-entry device, suchas a touch screen). As will be understood by one of ordinary skill inthe art, POI device 104 may be processed via any suitable securityprotocol and information about POI device 104 may be entered into anysuitable system, such as a separate KIF inventory management system.

As shown in FIG. 1, P2PE manager 166 may be operatively connected touser interface 180. User interface 180 may represent any number of userinterfaces configured to interact with P2PE manager 166 and userinterface 180 may be connected to P2PE manager 166 in any suitable way,such as via the Internet, LAN, WAN, Wi-Fi, etc. For example, userinterface 180 may represent a user interface at KIF 110 used to inputinformation regarding POI device 104 (as discussed above). Continuingwith this example, user interface 180 may also represent a userinterface at merchant 132 used to entered information regarding POIdevice 104 (e.g., when POI device 104 is received, to update the stateof POI device 104, etc.). User interface 180, in this example, mayrepresent a user interface at a third-party “Partner” (e.g., a hospitalusing an electronic medical records system or other entity wishing toencrypt and decrypt data). User interface 180 may be used to manuallychange the state of POI device 104 (e.g., from “Stored” to “Deployed”)or view the state of POI device 104, as shown at 182. In someembodiments, user interface 180, via P2PE manager 166, may be configuredto produce one or more reports 184 (as will be further discussedherein).

According to particular embodiments, once POI device 104 information isentered into P2PE manager 166, it is assigned a “state.” The state ofPOI device 104 as indicated in P2PE manager 166 may be used to helpensure secure handling and chain of custody of POI device 104. Forexample, when first entered into the P2PE manager 166, POI device 104 isassigned a state of “New” in the P2PE manager 166. Once a key has beeninjected into POI device 104, the state may be changed to “Injected.”Once received by a merchant (e.g., merchant 132), but not deployed/inuse, POI device 104 may have a state of “Stored.” Alternately, POIdevice 104 may be assigned a state of “DOA” (dead on arrival) if thedevice is damaged or non-functional. For example, P2PE manager 166 maybe configured to discard, prohibit and/or block data (e.g., card swipedata), from a POI device that is listed in a “Tampered,” “Dirty,” or“Flagged” state to protect the system and/or the card swipe data.

Continuing with FIG. 1, POI device 104 is stored at KIF 110 in a securedinventory room. The inventory room may be secured in any suitable way,such as, but not limited to, dual access, by lock and key, or by anysuitable security protocol.

According to particular embodiments, upon order from a merchant, POIdevice 104 is injected with one or more base derivation keys (“BDKs”)and is securely bagged, tagged, and packed for secure shipment to themerchant (e.g., merchant 132). According to at least one embodiment, ahardware security module (“HSM”) array produces encryption/decryptionkeys for encrypting data received by the POI device 104. As will beunderstood by one of ordinary skill in the art, an HSM array may belocated at a KIF or at a remote location. In the embodiment shown inFIG. 1, KIF 110 and HSM array 162 are remote.

HSM array 162, shown in FIG. 1 as part of P2PE system 160, in variousembodiments, creates a base derivation key (BDK), which is split intotwo parts, BDK 164A and BDK 164B for security purposes. BDK 164A and164B are sent to KIF 110 (via two separate secure pathways 186 and 188)where they are received by two key part holders. BDK 164A and 164B maybe sent to KIF 110 in any suitable manner, such as, for example, bycourier, by mail, by fax, by email (encrypted or otherwise), etc. Inparticular embodiments, the two key part holders verify receipt of BDK164A and BDK 164B via signature upon delivery, delivery receipt, etc.

In particular embodiments, the process continues with key assembly atstep 114. The key assembly process is briefly described immediatelybelow. However, it will be understood by one of ordinary skill in theart that this key assembly process is intended to be exemplary and anysuitable key assembly process may be used. The first key part holder(e.g., the person with BDK 164A) enters the secured inventory roomstoring POI device 104 and enters BDK 164A into a tamper resistantsecurity module (“TRSM”). The first key part holder leaves the securedinventory room. The second key part holder (e.g., the person with BDK164B) enters the secured inventory room (e.g., after the first key partholder has exited the secured inventory room) and enters BDK 164B intothe TRSM. According to particular embodiments, a third party separatelyvalidates the entries of the first key part holder and the second keypart holder (e.g., via a key serial number (KSN) and check digit). Uponauthentication of the key parts, the TRSM produces a cryptogramrepresenting the (assembled) BDK 164 and transfers the cryptogram to asmart card. POI device 104 (and each POI device) is injected with aunique Initial Key derived from the BDK (e.g., from the smart card). Asdiscussed herein, once POI device 104 is injected with the encryptionkey, its state in the P2PE manager 166 may be changed to “Injected” viatransmission 122.

Still referring to FIG. 1, at step 116, POI device 104 is placed in atamper evident bag and the bag is sealed with a tamper evident,serialized sticker. POI device 104 (in the tamper evident bag and sealedwith the serialized sticker) is then, at step 118, sealed in a box(e.g., any suitable shipping container) for shipment to merchant 132 andgiven a tracking number. According to particular embodiments, the serialnumber on the serialized sticker and the tracking number for theshipment of POI device 104 is entered into P2PE manager 166 viatransmission 124 and associated with the record for POI device 104 inP2PE manager 166 for later verification by merchant 132 upon receipt ofPOI device 104. In various embodiments, once a tracking number isentered into P2PE manager 166, the state associated with POI device 104may be changed.

At step 120, POI device 104 is securely shipped to merchant 132. POIdevice 104 may be securely shipped to merchant 132 in any suitable way,including by FedEx, UPS, USPS, etc. by air, ground, rail, etc.

Merchant 132 receives POI device 104 and registers receipt of POI device104 with P2PE manager 166 as shown at step 134 via transmission 126. Invarious embodiments, upon receipt of POI device 104, merchant 132confirms that the tamper evident bag (see above) and the serializedsticker used to pack POI device 104 have not been tampered with. Inparticular embodiments, merchant 132 enters the serial number of POIdevice 104 (as printed on the outside of the shipping box or in someother location) and the serial number of the serialized sticker intoP2PE manager 166. In one or more embodiments, the state associated withPOI device 104 is changed to “Stored” in P2PE manager 166. Merchant 132stores POI device 104 (in the tamper evident bag) until deployment.

At step 138, merchant 132 removes POI device 104 from the tamper evidentbag for deployment. In various embodiments, merchant 132 changes thestate of POI device 104 to “Deployed” in P2PE manager 166. It will beunderstood that, in various embodiments, P2PE manager 166 substantiallyautomatically changes the state of POI Device 104 to “Deployed” based onreceiving information (e.g., that the POI device 104 has been removedfrom the tamper evident bag).

At step 140, POI device 104 is deployed (e.g., connected a cashregister, etc.) to accept payment card information. As further discussedherein, POI device 104 may be configured to accept any payment (orother) information, but for the purposes of simplicity and brevity,payment card information in the form of magnetic card swipe data will bediscussed in regards to FIG. 1.

Upon receiving magnetic card swipe data (e.g., a first or initial cardswipe), in various embodiments, POI device 104 substantiallyautomatically encrypts the magnetic card swipe data based on theencryption key injected into POI device 104 at step 114 above. Invarious embodiments, POI device 104 is configured to encrypt the swipedata immediately after receiving the swipe data. In particularembodiments, POI device 104 may receive swipe data in any suitable way,including, via magnetic read heads (if a credit/debit card with amagstripe is swiped), via a chip and pin reader, via near-fieldcommunications, etc.

In FIG. 1, according to particular embodiments, upon receiving andencrypting swipe data, POI device 104 is configured to transmit theswipe data and other information (collectively, a “payload”) to paymentnetwork 190. According to particular embodiments, POI device 104'spayload includes, in addition to the swipe data, a serial numberassociated with POI device 104 (e.g., the serial number assigned to POIdevice 104 by manufacturer 102 and recorded in P2PE manager 166 at KIF110). In some embodiments, POI device 104's payload includes otherinformation including PIN information, biometric information (e.g., POIdevice includes or is connected to one or more biometric readers, suchas a finger print scanner), chip information, etc. It will be understoodby one of ordinary skill in the art that a POI device payload path asshown in FIG. 1 is merely exemplary and a POI device payload may berouted through one or more entities and/or via pathways not shown inFIG. 1.

At step 142, in response to receiving its first card swipe, POI device104 transmits its first payload to payment network 190, which forwardsthe payload to P2PE manager 166 for verification and decryption of theswipe data via internet 164 and transmission 146. In particularembodiments, upon receipt of the first payload from POI device 104, P2PEmanager 166 is configured to parse the first payload of POI device 104and extract the serial number of POI device 104. In some embodiments,P2PE manager 166 then compares the extracted serial number of POI device104 to a table of POI device serial numbers to determine whether POIdevice 104 is included in the table. In other words, in certainembodiments, P2PE manager 166 is configured to determine whether POIdevice 104 is a recognized device based on its serial number that issent to P2PE manager 166 with each transaction payload.

Upon determining that POI device 104's serial number is included in P2PEmanager 166, P2PE manager 166 may be configured to check the stateassociated with POI device 104. If, for example, POI device 104 has astate of “Deployed” in P2PE manager 166, upon successfully receiving thefirst swipe transaction, P2PE manager 166 may change the state of POIdevice 104 to “Active.” An “Active” state in P2PE manager 166 generallydenotes a state of securely receiving decrypted swipe transactions.

If, as another example, POI device 104 has a state of “Tampered” or“Stolen” or “Lost” in P2PE manager 166, P2PE manager 166 may beconfigured to discard the received payload and/or report the receipt ofa payload from a POI device that is not listed as “Active” or “Deployed”to merchant 132 or any other suitable party and not process theencrypted swipe data (e.g., included in the payload). It should beunderstood based on discussions herein that the system can help detectfraudulent transactions based at least in part on the various states ofP2PE manager 166. An exemplary list of state changes is shown at 182 inFIG. 1 and will be further discussed herein.

Continuing with the example shown in FIG. 1 wherein P2PE manager 166 hasreceived a first payload from POI device 104, P2PE manager 166 creates a“fingerprint” to be associated (in memory) with POI device 104 at step170. According to particular embodiments, the fingerprint for POI device104 is created by parsing the payload sent by POI device 104 andrecording the format, order, and number of data items included in thepayload (e.g., opposed to the contents of the payload) and/or anyfirmware versions of software running on POI device 104. Exemplaryfingerprint creation processes will be further discussed herein (e.g.,at FIG. 4A). In various embodiments, the fingerprint is stored and usedin future transactions to verify that data received from POI device 104is secure (e.g., that POI device 104 has not been tampered with and/oris not malfunctioning).

According the embodiment shown in FIG. 1, after the fingerprint analysis170, P2PE manager 166 transmits the first payload from POI device 104 toHSM 162 for decrypting (e.g., using BDK 164). Once the payload isdecrypted, the swipe data is re-encrypted to an encryption that can bedecrypted by other entities in the payment process. Once the payload isre-encrypted, it is transmitted to a payment network 190 where the swipedata (e.g., credit card information) is processed and sent on to anissuing bank 192 (money is debited from the consumer's accountassociated with the swiped card), acquiring bank 194, and finally to adepository bank 144 where money is deposited to the merchant (e.g.,merchant's bank account).

In particular embodiments, the system operates essentially in the sameway each time a payload is received from POI device 104 while the stateassociated with POI device 104 is “Active” (e.g., POI device 104regularly receives swipe transactions). For example, a customer ofmerchant 132 swipes their credit card at POI device 104. POI device 104transmits its payload, including POI device 104 serial number andencrypted swipe data to P2PE manager 166. Continuing with this example,P2PE manager 166 determines the serial number of the received payload(e.g., POI device 104's serial number) and looks up correspondingfingerprint information associated with POI device 104's serial numberto verify that POI device 104 has not been tampered with at step 170.Once POI device 104's fingerprint has been verified, in this example,HSM 162 decrypts POI device 104's payload and then re-encrypts the swipedata and sends it on to the payment network 190, issuing bank, 192,acquiring bank 194, and depository bank 144 to complete the paymentprocess.

Continuing with FIG. 1, if POI device 104 is tampered with (e.g., in anattempt to steal consumer data), P2PE manager 166 is configured to blockfraudulent transactions by not passing payloads to HSM 162 fordecryption as shown in step 174. There are a number of ways that P2PEmanager 166 may determine that POI device 104 has been tampered with andrefuse to pass the payload on to HSM 162 for decryption. In a particularembodiment, P2PE manager 166 may receive a payload from POI device 104that does not match the fingerprint associated with POI device 104(e.g., the format of the payload has changed, the version number of thefirmware used by the device has changed, etc.). In various embodiments,P2PE manager 166 may determine that a payload from POI device 104 hasbeen tampered with by receiving a payload from POI device 104 aftermerchant 132 has recorded that POI device 104's state is “In Repair,”“Damaged,” “Retired,” “Destroyed,” or “Stolen” (e.g., P2PE managershould not be receiving a payload from POI device 104 and thus will notdecrypt the payload). In many cases, if P2PE manager 166 determines thatPOI device 104 has been tampered with, then it will transmit anotification to merchant 132 and/or any other appropriate party, changethe state of POI device 104 in the POI database 168 to “Tampered” andwill no longer decrypt payloads from POI device 104.

System Architecture

FIGS. 2A, 2B, and 2C are block diagrams depicting exemplary systemarchitectures of the exemplary P2PE system of FIG. 1. Thesearchitectural components are organized into overarching processes forsecure handling of devices and payloads (e.g., for decryption): securedevice handling process 300, merchant data process 400, and P2PEManagement System 500. These major components are intended to beexemplary only and are used to assist in explaining the systems andmethods herein. As will be understood, the following architecturalcomponents may be operatively connected in any suitable way and mayinclude suitable processors, databases, firewalls, and the like.Further, the various components discussed herein may be distributed andoperatively connected in any suitable way. For example, in variousembodiments, the architectural components discussed below may bephysically connected and located in the same room and/or may beconnected via the Internet or private network and may be locatedremotely.

Secure POI Handling System Secure POI handling system 300 is more fullydescribed in this document in connection with FIG. 3. Secure POIhandling system 300, according to particular embodiments, includes apoint of interaction manufacturer 302 (e.g., manufacturer 102 in FIG. 1)that produces and ships a POI device 350 via secure handling proceduresto a key injection facility (KIF) 502. KIF 502 injects the POI device350 with an encryption key and securely ships POI device 350 to amerchant. POI device 350 is included in merchant data process 400 asfurther described herein.

POI manufacturer 302 manufactures devices that may be used with thesystems and methods discussed herein. POI manufacturer 302 maymanufacture any suitable device, including any POI device approved bythe PCI Security Standards Council (“PCI SSC”) or other suitable devicefor receiving information to be encrypted. Examples of PCI SSC-approveddevices can currently be found on PCI SSC's website athttps://www.pcisecuritystandards.org/approved_companies_providers/approved_pin_transaction_security.php.In one or more embodiments, POI device 350 is a stand-alone swipeterminal, such as ID TECH's SecuRED™ SRED device. In some embodiments,POI device 350 is an all in one type mobile business solution, such as4P Mobile Data Processing's FDA600-POS device. In at least oneembodiment, the POI device 350 is a countertop terminal, such as AtosWorldline's Yomani device.

As will be understood from discussions herein, POI manufacturer 302 ismerely an exemplary manufacturer. In various embodiments, the system maybe configured to decrypt any type of encrypted information (e.g., in a“decryption as a service” environment) from any suitable device. Inthese embodiments (and others), the manufacturer may produce anysuitable encryption device for encrypting social security numbers,driver license numbers, personal data, patient information, etc., andthus, may not necessarily produce POI devices. However, for the purposesof clarity of and brevity, a POI manufacturer and POI devices are shownin the figures.

It will be understood by one of ordinary skill in the art that merchantsand key injection personnel do not typically program POI devices (otherthan encryption key injection at a key injection facility). Thus, inmany of the embodiments discussed herein, POI manufacturer 302 loadsand/or programs POI device 350. In various embodiments, POI manufacturer302 configures POI device 350 with particular firmware and/or aparticular version of firmware. In further embodiments, POI manufacturer302 configures POI device 350 with various hardware and softwaresecurity features (e.g., software for encrypting swipe datasubstantially immediately after being read by POI device 350, hardwarethat destroys/erases any keys stored by POI device 350 upon tampering,etc.).

In particular embodiments, POI manufacturer 302 configures POI device350 to transmit a payload of information, where the payload includes aspecific set of information. In these (and other) embodiments, thepayload may include any suitable information such as device serialnumber and/or any other unique device identifier, unique identifier andversion number of the firmware installed on the device, date of devicemanufacture, device brand identifier, device model identifier, etc. Infurther related embodiments, the POI manufacturer 302 configures POIdevice 350 to transmit the payload in a particular format (e.g.,portions of data in a particular order, numbers in a particular formatsuch as hexadecimal, character, etc.). These configurations may be usedby P2PE Management System 500 (or 166) to identify particular POIdevices (e.g., POI device 350 and/or POI device 104 (FIG. 1) and toverify the authenticity of the received data via a fingerprint, as willbe further discusses in relation to FIGS. 5A and 5B.

Although not shown in FIGS. 2A, 2B, and 2C, POI manufacturer 302 mayinclude computing devices operatively connected to P2PE ManagementSystem 500 via any suitable connection.

KIF 502 includes any suitable computers, machines, etc. to receiveencryption keys 562, send and receive data 512, securely inject POIdevice 350 with an encryption key, bag POI device 350 with a serializedtamper-resistant bag, and ship POI device 350 to a merchant. Asdiscussed herein, in various embodiments, upon receipt of POI device350, a user enters (e.g., keys, scans, etc.) information associated withPOI device 350 into P2PE manager 166 (serial number, firmware versionnumber, etc.). In these embodiments, the user may enter the informationassociated with POI device 350 via a bar code scanner operativelyconnected to a computing device, via a keyboard operatively connected toa computing device, via a touchscreen interface operatively connected toa computing device, etc.

Computing devices located at the KIF may be any suitable computingdevices, including desktop computers, laptop computers, servers,tablets, other mobile devices, etc. In various embodiments, at leastsome of the computing devices located at the KIF are configured toconnect to the P2PE Management System 500 via a suitable user interface.In some embodiments, information is exchanged between computing deviceslocated at the KIF and the P2PE Management System 500 via email, http,or other suitable protocol.

According to particular embodiments, KIF 502 includes a tamper resistantsecurity module (“TRSM”) for assembling key parts (as discussed above,in various embodiments, the base derivation key is sent to the KIF intwo parts and is reassembled). The TRSM may be any suitable TRSMincorporating physical protections, including, for example,tamper-evident seals, hardened casings, and hardware and software toerase the contents of the TRSM upon detection of tampering. In variousembodiments, upon combining and validation of key parts, the TRSMproduces a cryptogram representing the base derivation key. In someembodiments, the cryptogram is transferred to a smart card.

The smartcard may be any suitable smartcard. In various embodiments, thesmartcard is a smartcard with a chip including one or more processorsfor key generation, signature, and/or encryption. In particularembodiments, the smartcard is equipped with software for creatingsuitable algorithms, such as hashing algorithms. In at least oneembodiment, the smartcard is operative for communicating with the TRSMand suitable key injection devices (e.g., Key Loading Devices, (KLDs)).The smartcard may include other features, such as tamper-resistantmeasures, tamper notification measures, anti-tearing measures, etc.

According to particular embodiments, the smart card is not used. Inthese embodiments (and others), the base derivation key is sent to theKIF in two parts and is reassembled as a KLD, without the use of thesmartcard.

In various embodiments, the KIF 502 includes one or more KLDs forinjecting POI devices with encryption keys. KLDs may be any suitable keyloading/key fill devices and, in various embodiments, are securecryptographic devices (SCDs).

According to various embodiments, once injected with an encryption key,POI device 350 is packaged in a tamper evident bag and shipped to themerchant for deployment.

Merchant Data System

As shown in the embodiments depicted in FIG. 2A, merchant data system400 includes POI device 350 deployed to receive payment transactions andPOI device 350 operatively connected to a payment transaction processor416. In FIG. 2A, third party transaction processor 416 as excluded fromP2PE Management System 500 (e.g., third party transaction processor 416is provided by a party other than the payment system, such as by themerchant or by a suitable partner). An exemplary merchant data processand an exemplary merchant P2PE report process are more fully describedin this document in connection with FIGS. 4A and 4B, respectively. Themerchant may include any suitable computing devices, point of saledevices, servers, databases, processors, etc.

As will be understood by one of ordinary skill in the art, POI device350 may be operatively connected to any suitable merchant point of salesystem. In various embodiments, POI device 350 is operatively connectedto a cash register, which may be digital, analog, touchscreen, etc.According to particular embodiments, POI device 350 is operativelyconnected to a mobile device, such as a mobile phone, tablet, etc.running software to accept payment information. In further embodiments,POI device 350 is operatively connected to a desktop computing devicefor completing sales.

In the embodiments shown in FIG. 2A, POI device 350 is operativelyconnected to payment transaction processor 416. It will be understood byone of ordinary skill in the art that POI device 350 may be directlyconnected to payment transaction processor 416 or may be indirectlyconnected to payment transaction processor 416 (e.g., POI device 350'spayloads are transmitted through other components of a point of salesystem to payment transaction processor 416). In various embodiments,third party transaction processor 416 may represent any suitable numberof servers, processors, etc. and may be located in any suitablelocation, including at the merchant or at a location remote from themerchant.

As shown in FIG. 2A, third party transaction processor 416 isoperatively connected (via Internet 209 or a private network (PN)) toone or more card networks 202, P2PE Management System 500, and issuer214. In this embodiment (and others), POI device 350 payloads aretransmitted to third party transaction processor 416, then, via Internet209, to the P2PE management system processes 500 for decryption andre-encryption, then the re-encrypted payment data is transmitted byInternet 209 and/or by PN to card networks 202.

The merchant system may include any number of suitable computing devices(not shown in FIG. 2A). These merchant computing devices may be anysuitable computing devices, such as desktop computers, laptop,computers, tablets, etc. and may be operatively connected to the P2PEManagement System 500. The merchant computing devices, in variousembodiments, enable users at the merchant to input information regardingPOI device 350 to be transmitted to P2PE Management System 500 (e.g.,state change information, tracking information, etc.). In one or moreembodiments, the merchant computing devices may also be configured toproduce various auditing reports regarding P2PE compliance.

P2PE Management System

In the embodiment shown in FIGS. 2A, 2B, and 2C, P2PE Management System500 may include any suitable software and/or hardware components,including servers, mobile computing devices, desktop computers, one ormore databases, and any number of suitable processors. According toparticular embodiments, P2PE Management System 500 is configured tomanage states of various POI devices (e.g., POI device 350). In theseembodiments (and others), P2PE Management System 500 may utilize anynumber of suitable tables and databases to store tables of informationregarding the various states of POI devices. In particular embodiments,P2PE Management System 500 includes one or more processors for receivingstate changes from computing devices, receiving information regardingstate changes of various POI devices, determining whether the state of aparticular POI device should be changed based on received information,etc.

According to various embodiments, P2PE Management System 500 includesone or more databases and one or more processors for receivingidentification data associated with various POI devices (e.g., POIdevice 350), such as a device serial number, a device (encryption) keyserial number, key sequence number, a device version number, a devicefirmware number/indicator, etc. In one or more embodiments, P2PEManagement System 500 is configured to store the received identificationinformation and, in at least one embodiment, indexing the identificationand other information associated with a particular POI device by thedevice serial number. For example, in a particular embodiment, P2PEManagement System 500 receives a payload of information from athird-party payment processor (e.g., the payment payload is sent from amerchant POI device to the third-party payment processor then to theP2PE management system) including a particular device serial number.Continuing with this example, P2PE Management System 500 is configuredfor parsing the payload to extract the particular device serial numberand for searching and locating additional device information based onthe particular device serial number.

As a second particular example, P2PE Management System 500 receives apayload of information from a third-party payment processor; however, inthis second particular example, the third-party payment processor sendsa portion of the payload, which has already been parsed. Continuing withthe second particular example, the P2PE management system 510 receives athird-party payment processor identifier, a key sequence number, and anyencrypted payment information to be decrypted.

In various embodiments, P2PE Management System 500 includes at least onedatabase and at least one processor for creating and storing identifiersassociated with POI devices (and/or any suitable encryption device orsystem). In some embodiments, P2PE Management System 500 is configuredto create a device identifier or “fingerprint” based on the format ofone or more payloads received from a particular POI device (e.g., POIdevice 350). In these embodiments (and others), P2PE Management System500 is configured to compare the format of future payloads received fromthe particular POI device to the fingerprint to verify the authenticityof the payload (e.g., that the payload has not been tampered with and/orcompromised in some way.).

According to one or more embodiments, P2PE Management System 500includes various processors and databases for creating audit reports formerchants. In these embodiments (and other embodiments), P2PE ManagementSystem 500 is configured to receive a request for an audit report from acomputing device associated with a merchant and access one or moretables configured to store information associated with various POIdevices associated with the merchant. P2PE Management System 500, inthese embodiments, is further configured to aggregate, summarize, andfacilitate the display (e.g., display on a screen of a computing deviceat the merchant, send to a printer of a computing device at themerchant, etc.) of the information associated with the various POIdevices associated with the merchant.

As will be understood by one of ordinary skill in the art, any of theabove mentioned processors may perform more than one function describedand any of the above mentioned databases may store more than one type ofinformation. Thus, the discussion above should not necessarily limit thevarious processors disclosed herein as having only the functionalitydiscussed above.

Now referring to FIG. 2B, an exemplary architecture of the P2PEManagement System 500 according to one embodiment of the present systemis shown. In various embodiments, the P2PE Management System 500 mayauthenticate and decrypt payloads received from one or more third partypartners. Each of the payloads received from the one or more third partypartners may have originated at a device, such as a POI device, oranother suitable system that transmits a payload for authentication anddecryption (e.g., a healthcare system, a governmental body, etc.).

According to particular embodiments, the one or more third partypartners may receive several thousand payloads per second from a largenetwork of devices, such as, for example, in embodiments where the oneor more third party partners are one or more payment processors that mayservice large retailers or many retailers. These payloads may requiredecryption so that the one or more third party partners can process theinformation contained within the payloads in real-time (e.g., real-timepayment processing). In various embodiments, P2PE Management System 500may be configured to authenticate and decrypt thousands of transactionsper second. In a particular embodiment, as will be further discussedhere, the P2PE Management System 500 may be configured to decrypt up to1600 payloads per second. In further embodiments, the P2PE ManagementSystem 500 may be scalable and configured to process many thousands ofpayloads per second.

The P2PE Management System 500 includes, in the embodiment shown in FIG.2B, a P2PE manager (e.g., P2PE manager 166) and a Decryption Web Server234. In various embodiments, the P2PE manager has the functionalitydescribed in FIG. 1 and comprises an Authentication Web Server 224, aRead-Only Database 228, a Master Read-Only Database 230, and aRead/Write Database 232. The P2PE Management System 500, in theembodiment shown in FIG. 2B, may be located behind a firewall 220 andoperatively connected to a load-balancer 222. In various embodiments,the load-balancer 222 comprises a combination of hardware, software,virtual machine, or other similar device that distributes workloadsbetween several computing devices. The load-balancer 222, in oneembodiment, may distribute and route payloads from the third partypartners to the Authentication Web Server 224, from the AuthenticationWeb Server 224 to the Decryption Web Server 234, and from the DecryptionWeb Server 234 to the third party partners (as processed, unencryptedpayloads). As will be understood by one of ordinary skill in the art,the P2PE Management System 500 is an exemplary embodiment only andvarious other components may be added, removed, or rearranged to providefunctionality as described herein.

The Authentication Web Server 224 (may also be referred to herein as a“frontend web server”) is a web server, which is, in variousembodiments, a combination of hardware, software, virtual machine, orother similar device that stores, processes, and delivers content tocomputing devices. In one embodiment, the Authentication Web Server 224may be hosted on a virtual machine and may authenticate the third partypartners that transmit payloads for decryption and the devices thatgenerated the payload. In one embodiment, the Authentication Web Server224 may be operatively connected to a Read-Only Database 228 and aload-balancer 222.

In various embodiments, the Authentication Web Server 224 mayauthenticate each payload received by the P2PE Management System 500 fordecryption. The Authentication Web Server 224 may confirm, in oneembodiment, that the partner requesting decryption is making a validrequest and that the format of the payload from a specific deviceconforms to the expected format of payloads received from the device. Inone embodiment, the Authentication Web Server 224 may determine that therequest for decryption was transmitted from an approved IP address, orthat the third party partner transmitted the appropriate identificationcredentials, or any other suitable method of identity authentication. Aswill be explained in further detail in conjunction with the descriptionof FIG. 5B, the Authentication Web Server 224 may compare thefingerprint (e.g., format, order, and number of data items included inthe payload) of the device that generated a particular payload to apreviously-stored device fingerprint for the specific device stored inthe Read-Only Database. If the fingerprints do not match, then, inparticular embodiments, the Authentication Web Server 224 denies thedecryption request and generates and sends an error log to a read/writedatabase.

Generally, when the P2PE Management System 500 receives a request fordecryption, the load-balancer 222 transmits the request andcorresponding payload to the Authentication Web Server 224. TheAuthentication Web Server 224, in one embodiment, may first validate thepartner that transmitted the request for decryption. In variousembodiments, this validation occurs, for example, by checking that therequest for decryption was generated from a known IP address that isassociated with the partner or that the partner transmitted the correctidentification number with the request or other similar and securemethod of authentication. The Authentication Web Server, in oneembodiment, after validating the partner, may validate the specificdevice that generated the payload. As will be explained in furtherdetail in conjunction with the description of FIG. 5B, theAuthentication Web Server 224, in various embodiments, may compare thefingerprint of the payload to the known device fingerprint of thespecific device. In one embodiment, if the fingerprints do not match,then the Authentication Web Server 224 may reject the decryption requestand transmit a decryption exception log to the Read/Write Database 232.According to one embodiment, if the fingerprints match, then theAuthentication Web Server 224 may transmit the payload to the loadbalancer 222 (which may transmit it to the Decryption Web Server 234)and may transmit a decryption log to the Read/Write Database 232.

In various embodiments, the Authentication Web Server 224 comprises aplurality of Authentication Nodes 226. Authentication Nodes 226 may be,in one embodiment, applications designed to process the authenticationsof partners and device payloads by accessing the Read-Only Database 228.In one embodiment, Authentication Nodes 226 may be configured to createlogs of authentications and exceptions and to transmit those logs to theRead/Write Database 232. In one embodiment, to process 1,600 payloadsper second, the Authentication Web Server 224 comprises threeAuthentication Nodes 226.

The Read-Only Database 228 comprises a database, which is, in variousembodiments, a combination of hardware, software, virtual machine, orother similar device that is an organized collection of data (e.g.,containing data tables, etc.). In one embodiment, the Read-Only Database228 may contain data necessary for authenticating the payloads andrequests for decryption and may be hosted as a virtual machine on theAuthentication Web Server 224.

In one embodiment, the Read-Only Database 228 may be operativelyconnected to the Authentication Web Server 224 and the Master Read-OnlyDatabase 230. The Read-Only Database 228 may be configured, in oneembodiment, for storing read-only authentication data for use indetermining whether payloads have been compromised and authenticatingthird party partners. In one embodiment, the Read-Only Database 228 maybe configured for storing read-only authentication data for use indetermining whether a third party partner is the appropriate entity tobe making the decryption request. As will be appreciated by one havingordinary skill in the art, as the Read-Only Database 228 may beread-only from the perspective of the Authentication Web Server 224, theRead-Only Database 228 may not be configured to write write-requestsfrom the Authentication Web Server 224 and instead may transmit them tothe Master Read-Only Database 230.

After receiving a payload and request for decryption, in one embodiment,the Authentication Web Server 224 may query the Read-Only Database 228to determine whether the payload is valid or has been compromised (e.g.,by authentication and validation). In one embodiment, the AuthenticationWeb Server 224 may query the Read-Only Database 228 to determine thevalidity of the third party partner that transmitted the payload (e.g.,by transmitting the firmware number or serial number of the device asfurther discussed herein). The Read-Only Database 228, in oneembodiment, transmits a response to the query back to the AuthenticationWeb Server 224. If the response confirms the validity of the third partypartner, then the Authentication Web Server 224 may query the Read-OnlyDatabase 228 to determine the validity of the payload of the device. TheRead-Only Database 228, in one embodiment, may transmit a response tothe query back to the Authentication Web Server 224 that includes datanecessary to validate the payload. In one embodiment, the AuthenticationWeb Server 224 may compare the payload to the response from theRead-Only Database 228 to determine the validity of the payload. If thecomparison confirms the validity of the payload of the device, then theAuthentication Web Server 224 may transmit a log of the decryptionrequest to the Read-Only Database 228. If either the third party partneror payload is invalid, then the Authentication Web Server 224 maytransmit an exception log to the Read-Only Database 228. In embodimentswhere the Read-Only Database 228 is read-only from the perspective ofthe Authentication Web Server 224, the Read-Only Database 228 maytransmit exception logs and logs of decryption requests to the MasterRead-Only Database 230.

As will be appreciated by one having ordinary skill in the art, theread-only perspective of the Read-Only Database 228 may permit theAuthentication Web Server 224 to query the Read-Only Database 228 andthe Read-Only Database 228 to respond to those queries faster than ifthe Read-Only Database 228 were configured with read/writefunctionality. In one embodiment, the Read-Only Database 228 includes aMONGO—formatted database or any other NoSQL format that enables thedatabase to handle the necessary requests per second (e.g., up to about1600 per second). As will be appreciated by one having ordinary skill inthe art, this type of database is easily refreshable and can beconfigured to operate quickly as it is not as robust a data structure asa relational database. In one embodiment, the data stored in thedatabase need not be associated with other data (e.g., the data isstored in collections of individual data objects). Further, in variousembodiments, the Read-Only Database 230 may be configured to not confirmwrite-requests so that the database can perform more write-requests persecond. In various embodiments, to avoid the potential data losses thataccompany this functionality, the Read-Only Database 228 may beoperatively connected to a Master Read-Only Database 230.

The Master Read-Only Database 230 includes a database, which is, invarious embodiments, a combination of hardware, software, virtualmachine, or other similar device that is an organized collection of data(e.g., containing data tables, etc.). In one embodiment, the MasterRead-Only Database 230 may contain data necessary for refreshing theRead-Only Database 228 and may be hosted as a virtual machine on theAuthentication Web Server 224.

In one embodiment, the Master Read-Only Database 230 may be operativelyconnected to the Read-Only Database 228, the MQTT Queues 231, and theRead/Write Database 232. The Master Read-Only Database 230 may beconfigured, in one embodiment, for receiving and storing authenticationdata received from the Read/Write Database 232 for refreshing theRead-Only Database 228. In various embodiments, the Master Read-OnlyDatabase 230 may be read-only from the perspective of the Read-OnlyDatabase 228 and read/write from the perspective of the Read/WriteDatabase 232. As will be appreciated by one having ordinary skill in theart, as the Master Read-Only Database 230 may be read-only from theperspective of the Read-Only Database 228, the Master Read-Only Database230 may not be configured to write write-requests from the Read-OnlyDatabase 228 and instead may transmit them to the MQTT Queues 231 andthe Read/Write Database 232.

In one embodiment, the Master Read-Only Database 230 may receive logsfrom the Read-Only Database 228 and may transmit those logs to the MQTTQueues 231 and the Read/Write Database 232. The Master Read-OnlyDatabase 230, in one embodiment, may receive updates from the Read/WriteDatabase 232, refresh its data tables based on the updates, and transmitthe updates to the Read-Only Database 228. As will be appreciated by onehaving ordinary skill in the art, the Master Read-Only Database 230 mayprevent data loss between the Read-Only Database 228 and the Read/WriteDatabase 232.

In one embodiment, the Master Read-Only Database 230 includes aMONGO-formatted database or any other NoSQL format that enables thedatabase to handle the necessary requests per second. As will beappreciated by one having ordinary skill in the art, this type ofdatabase may be easily refreshable and can be configured to operatequickly as it is not as robust a data structure as a relationaldatabase. In one embodiment, the data stored in the database need not beassociated with other data (e.g., the data is stored in collections ofindividual data objects). Further, the Master Read-Only Database 230, invarious embodiments, may be configured to perform write-requests withoutconfirming them so that the database can perform more write-requests persecond. To avoid the potential data losses that accompany thisfunctionality, the Master Read-Only Database 230 may be operativelyconnected to the Read/Write Database 232 and the MQTT Queues 231.

The MQTT Queues 231 includes a message queuing protocol for storingmessages (e.g., log write-requests). In one embodiment, the MQTT Queues231 may be operatively connected to the Master Read-Only Database 230and the Read/Write Database 232. In one embodiment, the MQTT Queues 231may be within a separate partition within the same hardware, software,virtual machine, or other similar device that hosts the Master Read-OnlyDatabase 230. The MQTT Queues 231 may be configured, in one embodiment,with a queuing protocol for receiving, queuing, and transmitting themessages (e.g., logs, events exceptions, etc.) transmitted from theMaster Read-Only Database 230 via the message queuing protocol to theRead/Write Database 232. In various embodiments, the MQTT Queues 231 mayprocess the messages to the Read/Write Database 232 via message queuetelemetry transport messaging protocol (e.g., MQTT).

In one embodiment, the MQTT Queues 231 may receive messages from theMaster Read-Only Database 230 and store those messages within its queueusing a message queuing protocol until a particular event or set ofcircumstances occurs. In one embodiment, this functionality enables theMQTT Queues 231 to function as a back-up for messages transmitted by theAuthentication Web Server 224 to be received by the Read/Write Database232. As will be appreciated by one having ordinary skill in the art, theMQTT Queues 231 may prevent data loss between the Master Read-OnlyDatabase 230 and the Read/Write Database 232. Further, the MQTT Queues231 may permit the P2PE Management System 500 to operate normally evenif the Read/Write Database 232 is offline. Generally, the MQTT Queues231 may store log write-requests received from the Read-Only Database230 and the Read-Only Database 228; thus, in one embodiment, the logwrite-requests may be queued until the Read/Write Database 232 can writethe log write-requests, which may prevent the loss of any logwrite-requests generated when the Read/Write Database 232 is notoperating.

In one embodiment, upon determining that less than a particular numberof payloads are being processed per second by the P2PE Management System500, the MQTT Queues 231 may transmit messages from its queue to theRead/Write Database 232. For example, if the P2PE Management System 500is processing less than 250 (or, e.g., 500, 750, 1,000, etc.) payloadsper second, then the MQTT Queues 231 may be configured to transmit themessages in its queue. In a particular embodiment, if the P2PEManagement System 500 is processing less than 500 payloads per second,then the MQTT Queues 231 may begin transmitting messages to theRead/Write Database 232 until either all of the messages have beentransmitted or the system begins processing more than 500 payloads persecond. If all of the messages have been transmitted, then the MQTTQueues may stop transmitting messages and may wait to receive moremessages from the Master Read-Only Database 230. If the P2PE ManagementSystem 500 begins processing more than 500 payloads per second, then theMQTT Queues 231 may stop transmitting messages and may wait to begintransmitting messages again until the P2PE Management System 500 isprocessing less than 500 payloads per second. As will be appreciated byone having ordinary skill in the art, the MQTT Queues 231 may receivemessages from the Master Read-Only Database 230 regardless of whether itis transmitting messages to the Read/Write Database 232.

The Read/Write Database 232 (may also be referred to herein as a“backend read/write database”) is a database, which includes, in variousembodiments, a combination of hardware, software, virtual machine, orother similar device and is an organized collection of data (e.g.,containing data tables, etc.). In one embodiment, the Read/WriteDatabase 232 may contain data necessary for authenticating anddecrypting payloads from third party partners, and substantially all ofthe messages generated by the Authentication Web Server 224 andDecryption Web Server 234 and may be hosted as a virtual machine.According to various embodiments, the Read/Write Database 232 mayperform the major functions of the P2PE manager 166, as describe inrelation to FIG. 1, other than the functionality of the AuthenticationWeb Server 224 and databases as previously described. In variousembodiments, the Read/Write Database 232 may receive state changes fordevices, such as via transmission 122, 124, and 126, and may receiveserial numbers for devices. In one embodiment, the Read/Write Database232 may update its data tables based on the received state changes andserial numbers.

In one embodiment, the Read/Write Database 232 may be operativelyconnected to the Master Read-Only Database 230, the MQTT Queues 231, andthe Decryption Web Server 234. The Read/Write Database 232 may beconfigured, in one embodiment, for storing and transmittingauthentication data to the Master Read-Only Database 230, receiving andstoring messages from the MQTT Queues 231, updating the authenticationdata based on the exception messages, and transmitting updates for theRead-Only Database 228 to the Master Read-Only Database 230. In oneembodiment, the Read/Write Database 232 includes a MYSQL-formatteddatabase. As will be appreciated by one having ordinary skill in theart, a MYSQL database includes a relational database management system,which may allow the Read/Write Database 232 to store logs in associationwith the third party partners and POI that generated those logs, and maybe easily compatible with multiple systems, which may allow the P2PEManagement System 500 to interface with multiple outside systems forfunctions including, but not limited to, auditing, billing, etc.

In one embodiment, the Read/Write Database 232 may receive messages fromthe MQTT Queues 231. If those messages are authentication logs, then theRead/Write Database 232 may store and associate the logs with the thirdparty partner and device that generated the payload that wasauthenticated. If those messages are exception logs, then the Read/WriteDatabase may stores those logs and may update the records of the thirdparty partner and device that generated the payload to reflect theexception. In one embodiment, the Read/Write Database 232 may transmitupdates to the Master Read-Only Database 230 to refresh both the MasterRead-Only Database 230 and the Read-Only Database 228.

According to various embodiments, the Read/Write Database 232 mayreceive decryption logs and decryption exception logs from theDecryption Web Server 234. The decryption logs may indicate a successfuldecryption of a payload and may be stored in relation to the associatedpartner, device, and payload for the decryption within the Read/WriteDatabase 232. The decryption exception logs may indicate an unsuccessfuldecryption of a payload and may be stored in relation to the associatedpartner, device, and/or payload for the decryption within the Read/WriteDatabase 232. One skilled in the art will appreciate that these logspermit the P2PE Management System 500 to produce reports regarding thenumber of payloads decrypted, unsuccessful payload decryptions, etc. Invarious embodiments, the decryption logs and decryption exception logsfrom the Decryption Web Server 234 may be queued before beingtransmitted to the Read/Write Database 232 in a process similar to thatfor authentication logs and exceptions logs on the MQTT Queues 231 asdiscussed previously herein.

The Decryption Web Server 234 includes a web server, which is, invarious embodiments, a combination of hardware, software, virtualmachine, or other similar device that stores, processes, and deliverscontent to computing devices. In one embodiment, the Decryption WebServer 234 may be hosted on a virtual machine and may decrypt payloadsreceived from third party partners. In one embodiment, the DecryptionWeb Server 234 may be operatively connected to the Read/Write Database232 and the load-balancer 222.

In various embodiments, the Decryption Web Server 224 may decrypt eachpayload received by the P2PE Management System 500 for decryption.According to various embodiments, the Decryption Web Server 224 may beresponsible for determining the appropriate decryption algorithm todecrypt the payload, decrypting the payload, confirming decryption,transmitting the decrypted payload back to the load-balancer 22, andgenerating a log of the decryption.

Generally, when the P2PE Management System 500 receives a request fordecryption, the load-balancer 222 transmits the request andcorresponding payload to the Authentication Web Server 224. In oneembodiment, the Authentication Web Server 224 may parse the payload,prior to transmitting the request back to the load-balancer 222, todetermine the key index for that particular payload. Generally, a keyindex indicates a base key (e.g., algorithm) used as the basis forencrypting a payload of the particular device and will be betterunderstood in connection with the description of FIGS. 6, 11, 12, etc.After the Authentication Web Server 224 authenticates the third partypartner and payload, in one embodiment, the Authentication Web Server224 may transmit the request, key index, and corresponding payload backto the load-balancer 222, which may transmit the request, key index, andcorresponding payload to the Decryption Web Server 234. According to adifferent embodiment, the Decryption Web Server 234 may determine theappropriate decryption algorithm to decrypt the payload, decrypt thepayload, and confirm that the decryption was successful (e.g., confirmsthat the decrypted payload contains credit card information as expectedand not random data). In various embodiments, the Decryption Web Server234 may transmit the decrypted payload back to the load-balancer 222,which may transmit the decrypted payload to the third party partner, andgenerate a log of the decryption. In one embodiment, the Decryption WebServer 234 may transmit that log of the decryption to the Read/WriteDatabase 232.

In various embodiments, the Decryption Web Server 234 includes aHardware Security Module 238 (e.g., HSM). In various embodiments, theHSM 238 may receive the request, key index, and corresponding payloadfrom the Decryption Web Server 234. Generally, in various embodiments,the HSM 238 may process the key index to determine the appropriatemethod to use to decrypt the payload, decrypt the payload, confirmdecryption, transmit the decrypted payload back to the load-balancer 22,and generate a log of decryption. In one embodiment, the HSM 238 maydetermine the appropriate decryption algorithm to decrypt the payload,decrypt the payload, confirm decryption, transmit the decrypted payloadback to the load-balancer 22, and generate a log of the decryption. Invarious embodiments, HSM 238 includes suitable one or more processorsand one or more databases for creating and storing encryption keys. Inparticular embodiments, HSM 238 includes at least one processor and atleast one database for receiving payloads, for deriving encryption keysfrom payload information, for decrypting payment data included in suchpayloads, re-encrypting at least a portion of a payload, including thepayment information, and transmitting the re-encrypted portion of thepayload to a card network (e.g., card network 202) via the Internet 209and/or a private network (PN). Generally, HSM 238 can decrypt payloadsin any format (e.g., TDES/3DES, DUKPT, format-preserving encryption(e.g., BPS), base64 encoded, hexadecimal encoded, encrypted value name,etc.) HSMs will be further understood in relation to the description ofFIGS. 1, 4, 5, 6, etc.

According to particular embodiments HSM 238 includes a device thatprovides FIPS 104-2 Level 3 certified physical and logical protection tocryptographic keys or other suitable PCI-compliant HSM. An example ofsuch an HSM is the SafeNet Luna EFT HSM. Other examples of PCI approvedHSMs can be found athttps://www.pcisecuritystandards.org/approved_companies_providers/approved_pin_transaction_security.php.

Generally, a HSM may process up to 1,600 payloads per second. Tounderstand how the P2PE Management System 500 handles more than 1,600payloads per second, a discussion of the scalability of the P2PEManagement System 500 may be useful.

Now referring to FIG. 2C, an exemplary architecture of the P2PEManagement System 500 according to one embodiment of the present systemis shown. In various embodiments, the P2PE Management System 500 may bescalable to enable the P2PE Management System 500 to decrypt morepayloads per second.

The scalability of P2PE Management System 500, in one embodiment, maynot be dependent on any one component of the system but may instead bebased on the desired number of decryptions per second. Accordingly, inone embodiment, the P2PE Management System 500 may be expanded based onone rate-limiting component, and all other components may be scaledbased on that rate-limiting component. According to various embodiments,the scalability of the P2PE Management System 500 may be based on thenumber of HSMs 238 in the P2PE Management System 500 (e.g., therate-limiting component). For example, the HSM 238 generally may processup to about 1,600 decryptions (e.g., payloads) per second. If 3,200decryptions per second are desired, then the P2PE Management System 500,in one embodiment, should include two Decryption Web Servers 234, eachincluding one HSM 238, (or, alternatively, one Decryption Web Server 234including two HSMs 238) operatively connected to a load-balancer 222 anda Read/Write Database 232. To support two HSMs 238 processing up toabout 3,200 decryptions per second, then the P2PE Management System 500,in one embodiment, includes three Authentication Web Servers 224. Inthis embodiment, each of the three Authentication Web Servers 224 may beoperatively connected to the load-balancer 222 and a Read-Only Database228. Continuing with this embodiment, the system includes threeRead-Only Databases 228 operatively connected to the Master Read-OnlyDatabase 230, which may be operatively connected to the MQTT Queues 231and Read/Write Database 232. With this configuration, in one embodiment,the P2PE Management System 500 may authenticate and validate up to about3,200 payloads per second and the HSMs 238 become the rate-limitingcomponent of the P2PE Management System 500.

In one embodiment, when the P2PE Management System 500 includes multipleRead-Only Databases 228, the Master Read-Only Database 230 may refreshthe Read-Only Databases 228 at substantially the same time bytransmitting the same update to each Read-Only Database 228. Similarly,in one embodiment, when the P2PE Management System 500 includes multipleRead-Only Databases 228, the Master Read-Only Database 230 may receiveauthentication logs and exception logs from each of the Read-OnlyDatabases 228 at substantially the same time and pass those messagesinto the same MQTT Queues 231 for transmission to the Read/WriteDatabase 232.

According to various embodiments, the P2PE Management System 500includes only one Master Read-Only Database 230, MQTT Queues 231, andRead/Write Database 232, regardless of the number of Authentication WebServers 224, Read-Only Databases 228, Decryption Web Servers 234, andHSMs 238. According to various embodiments, to process up to about 6,400payloads per second, the P2PE Management System 500 includes fourDecryption Web Servers 234, four HSMs 238, six Authentication WebServers 224, six Read-Only Databases 228, one Master Read-Only Database230, one MQTT Queues 231, and one Read/Write Database 232.

According to various embodiments, to process up to about 12,800 payloadsper second, the P2PE Management System 500 includes eight Decryption WebServers 234, eight HSMs 238, twelve Authentication Web Servers 224,twelve Read-Only Databases 228, one Master Read-Only Database 230, oneMQTT Queues 231, and one Read/Write Database 232.

Exemplary System Processes Exemplary POI Handling Process (FIG. 3)

FIG. 3 depicts a high-level flow chart of an exemplary secure devicehandling process 300 as shown in FIG. 2A. In various embodiments, thisPOI handling process may help verify a secure chain of custody for a POIdevice. To briefly summarize, in a particular embodiment, as a POIdevice is transported from and handled by different entities, the POIManager assign various states to the POI device. In these particularembodiments (and others), the POI Manager verifies that the POI devicehas been assigned the correct sequence of states before facilitating thedecryption of a payload of the POI device. This secure POI handlingprocess, in particular embodiments, helps identify whether POI deviceshave been tampered with and/or switched (e.g., with a nefarious POIdevice) during the transport of a POI device between the time ofmanufacture to the time of deployment at a merchant. POI handlingprocess 300, as shown in FIG. 3 and described immediately below may helpillustrate at least one embodiment of this POI handling process.

Beginning at step 330, the system is configured to receive particularPOI device identification information at the P2PE Management System 500.In various embodiments, the particular POI device identificationinformation includes a serial number associated with the particular POIdevice (e.g., POI device 350 in FIG. 2A). In particular embodiments, theparticular POI device identification information includes version of thefirmware installed on the particular POI device. In further embodiments,the particular POI device identification information includes any othersuitable information, such as model, device type, device manufacturedate, etc.

The system may be configured to receive the particular POI deviceidentification information from any suitable entity in any suitable way.In particular embodiments, the particular POI device identificationinformation is transmitted (e.g., via encrypted electronic packets) froma computing device at a key injection facility (KIF). In someembodiments, the particular POI device identification information isreceived from a computing device associated with the manufacturer. Infurther embodiments, the particular POI device identificationinformation is input by a person into a computing device operativelyconnected to the POI Manager.

At step 332, the system is configured to, in response to receiving theparticular information associated with POI device 350, set the state ofPOI device 350 to indicate that the POI device is new/ready forprogramming. (e.g., the system is configured to set the state of theparticular POI device to “New”). In various embodiments the system isconfigured to change the state of the POI device to New by adding thePOI device (or associated identifier) to a table or list of POI deviceswith a New status. In further embodiments, the system is configured tochange the state of the POI device by including the state of the POIdevice in a table with a POI device identifier (e.g., the POI device islisted by identifier on a table and the state associated with the POIdevice changes). In still further embodiments, the informationassociated with the POI device in the system may include various bitsthat indicate a state (e.g., information about POI devices include bitsindicating each state and can be set to on or off to indicate the stateof the device). In this embodiments (and others), the system may beconfigured to change the bit associated with the New state to on or to“1”.

At step 334, the system is configured to receive an indication that theparticular POI device is injected with an encryption key. As discussedherein, in various embodiments, POI devices are stored at a KIF untilthey are injected. In some embodiments, once the particular POI deviceis ordered from a merchant (or at any other suitable time), theparticular POI device is injected with an encryption key under specialsecurity protocol (as discussed elsewhere herein).

The system may be configured to receive the indication that theparticular POI device is injected with the encryption key in anysuitable way. According to particular embodiments, once injected, a userat the KIF logs into the P2PE Manager (via a suitable computing device)and indicates that the particular POI device has been injected. In someembodiments, the system may be configured to receive the indication thatthe particular POI device is injected automatically from a computingdevice linked to the key injection equipment and/or certain protocoldevices associated with injecting the particular POI device.

At step 336, based at least in part on receiving the indication that theparticular POI device is injected with the encryption key, the system isconfigured to change the state of the particular POI device to indicatethat the POI device has been injected (e.g., assign an “Injected”state). In particular embodiments, the system is configured to receivethe indication that the particular POI device is injected by a usermanually changing the status of the particular POI device from New to“Injected.” The system may be configured to change the state of the POIdevice in any suitable way, including (but not limited to) the waysdiscussed in relation to changing the particular POI device state to“New” at step 332.

At step 338, the system is configured to receive information regardingshipping the particular POI device. In various embodiments, theparticular POI device is packed for shipment from the KIF to a merchant.In these embodiments (and others), the system is configured to receivevarious information regarding the shipping of the particular POI devicesuch as a tamper-resistant bag number (e.g., serial number), a boxnumber, a tracking number, merchant number, address/shippingdestination, and/or any other suitable information for tracking and/orverifying the shipment of the particular POI device.

At step 340, the system is configured to receive data from a merchantindicating receipt of the particular POI device. In various embodiments,the system is configured to receive the data from the merchantindicating receipt of the particular POI device by receiving the serialnumber of the particular POI device. In particular embodiments, thesystem is configured to receive the data from the merchant indicatingreceipt of the particular POI device by receiving the tracking numberand/or tamper resistant bag serial number associated with the POIdevice. In some embodiments, the system may be configured to receive thedata indicating the receipt of the particular POI device in any othersuitable way.

At step 342, based on receiving the data from the merchant, the systemis configured to determine whether the particular POI device has beencompromised during shipment. In various embodiments, the system isconfigured to determine whether the particular POI device has beencompromised during shipment by comparing the data received from themerchant (e.g., at step 340) to the information regarding shipping theparticular POI device (e.g., at step 338). According to particularembodiments, the system is configured to look up the device based on thedevice serial number and verify that the tracking information, tamperresistant bag serial number, etc. match. In these embodiments, thesystem verifies these numbers/identifiers to ensure that the particularPOI device has been shipped from the KIF to the merchant withouttampering or without someone swapping out the particular POI device(e.g., for a POI device that is programmed to send cardholderinformation to another location or any other nefarious task).

The system may be configured to compare the data received from themerchant to the information regarding shipping the particular POI devicein any suitable way. In various embodiments, the system is configured tostore the information regarding the shipping the particular POI devicein a table associated with the particular POI device's serial number(e.g., a serial number created by the manufacturer and input to thesystem at the KIF). In these embodiments, upon receipt of the serialnumber and data from the merchant indicating receipt of the particularPOI device (e.g., the information at step 340), the system is configuredto look up the information regarding shipping the particular POI deviceby looking up the particular POI device's serial number and accessing atable with the appropriate header (e.g., “KIF shipping information” orthe like) to find the information regarding shipping the particular POIdevice.

At step 344, the system is configured to change the state of theparticular POI device to indicate that the particular POI device hasbeen received by the merchant (but not deployed). In variousembodiments, the system is configured to change the state of the POIdevice to “Stored” to indicate that the particular POI device is storedat the merchant.

The system may be configured to change the state of the particular POIdevice in any suitable way. In various embodiments, the system isconfigured to change the state of the particular POI device by receivingan indication to change the state of the particular POI device from acomputing device associated with the merchant (e.g., a user selects orinputs a notification to change the state of the particular POI device).According to particular embodiments, the system is configured toautomatically change the state of the particular POI device upondetermining that the particular POI device has not been compromisedduring shipment (e.g., at step 342).

At step 346, the system is configured to receive an indication that theparticular POI device is deployed. In various embodiments, the systemmay receive an indication from a computing device (e.g., a manualindication from a user) that the particular POI device is deployed(e.g., ready to receive swipe transactions). In one or more embodiments,the system is configured to receive an indication that the particularPOI device is deployed by receiving an indication at a user-interfacethat the particular POI device is ready for deployment, and in response,the system changes the state of the particular POI device to indicateddeployment (e.g., changes the state of the POI device from “Stored” to“Deployed”).

It should be understood by one of ordinary skill in the art and from thediscussions herein that the state of the particular POI device maychange and/or vary from the sequence discussed above. In a particularexample, the merchant could receive the particular POI device anddetermine that it is damaged. Continuing with this particular example,the merchant could then indicate to the system that the particular POIdevice is damaged and the system could change the state of theparticular POI device to indicate that the POI device is damaged (e.g.,a “Damaged” state). As discussed below, once in the Deployed state, theparticular POI device (e.g., POI device 350) is ready to receive swipedata, as described below in reference to FIG. 4A.

Exemplary Merchant Data Process (FIG. 4A)

Referring to FIG. 3, above, once a particular POI device (e.g., POIdevice 350), is received by a merchant and deployed, the particular POIdevice is, in various embodiments, ready to receive customertransactions. As will be understood by one of ordinary skill in the art,the particular POI device may require additional set-up by the merchant,such as, for example, connection to a payment processing computingdevice, additional software set-up, etc.

Turning to FIG. 4, at step 430, the particular POI device receivescustomer data. As discussed herein, the particular POI device mayreceive payment transaction data (card swipe data, etc.) and othercustomer verification information, such as, for example, biometric data(finger print, retinal scan, etc.) chip and pin data, PIN data, etc.

At step 432, immediately upon receiving the customer data, theparticular POI device is configured to encrypt the customer data. Invarious embodiments, the particular POI device may be configured toencrypt the customer data based on the encryption key(s) that have beeninjected. In some embodiments, the particular POI device is configuredto encrypt the customer data via an internal encryption scheme. Infurther embodiments, the particular POI device is configured to encryptthe customer data via an encryption key that is sent to particular POIdevice with each transaction.

At step 434, the particular POI device is configured to compile apayload to be transmitted to a payment processor. In variousembodiments, the payload includes the encrypted customer data. In one ormore embodiments, the payload includes the device serial number. In atleast one embodiment, the payload includes the device serial numberand/or firmware number. In further embodiments, the payload includes amanufacture date of the particular POI device. In still furtherembodiments, the payload includes various other information such as anencrypted PIN or other verification information associated with acustomer and/or other information to identify the transaction (e.g.,date of transaction, merchant, cashier number, etc.).

The particular POI device may be configured to compile the payload inany suitable format, which may be used by the system to create afingerprint for the particular POI device as discussed herein. Invarious embodiments, the particular POI device is configured to compilethe payload in a string of data representing various data items of thepayload. In these embodiments (and others), various components of thepayload string may be formatted in character, XML, or hexadecimalformat.

The payload may include any suitable components. In various embodiments,the payload includes an indication of the format of the components(e.g., hexadecimal, XML, etc.). In particular embodiments, the payloadincludes an indication of the particular encryption (cypher) algorithm,such as, for example, RAW (e.g., data is unencrypted), triple dataencryption standard (“TDES” or “3DES”) indicating that the DES derivedunique key per transaction (“DUKPT”) encryption scheme has been used toencrypt the payload data, advanced encryption standard indicating thatthe AES DUKPT encryption scheme has been used to encrypt the payloaddata.

In various embodiments, the P2PE Manager includes an indication of aparticular type of encryption associated with a particular device basedon the particular device's serial number. In these embodiments, andothers, the system is configured to transmit an indication of theparticular type of encryption to the HSM based on the particular devicesserial number.

According to particular embodiments, the payload includes card swipedata. The card swipe data may include any or all of the various tracksof data encoded in a card's magnetic stripe. As will be understood byone of ordinary skill in the art, in various embodiments, a card'smagnetic stripe contains three distinct tracks of encoded data, eachread by a magnetic card reader. In these embodiments, the system may beconfigured to encrypt and compile each track of card data. In someembodiments, each track of card data may include different information.In further embodiments, each track of card data may include at leastsome of the same information.

The particular POI device may be configured to compile each track ofcard data in any suitable way. In various embodiments, the particularPOI device is configured to compile each track of card swipe data ascard track format with each track formatted as a clear set of data(e.g., no encryption), followed by an encrypted set of data (e.g., thecard swipe data for the particular track), followed by a dummy set ofencrypted data (e.g., encrypted random data that does not represent thecard swipe data). In particular embodiments, each of the clear,encrypted, and dummy sets of data may be in a character or hexadecimalformat.

The particular POI device may output the above described data, forexample, in the following format:

-   -   FORMAT_CIPHERED_[TRACK1][_TRACK2][_TRACK3]

The particular POI device may be configured to include additional datain the payload. According to particular embodiments, the particular POIdevice is configured to include a key serial number (“KSN”) and/ordevice serial number (“DSN”) in the payload (e.g., a key serial numberindicating how the HSM should decrypt the various encrypted tracks and adevice serial number as discussed herein to identify the particular POIdevice). In these embodiments (and others) the KSN and DSN may beformatted in either character or hexadecimal format. In furtherembodiments, the particular POI device is configured to include ahardware version number and/or a firmware version number, each of whichmay be formatted in character or hexadecimal format (or may be empty).As will be understood by one of ordinary skill in the art, the abovecomponents of the payload may be formatted in any suitable format andmay arranged in the payload in any suitable way. For example, the TRACK1data above may come before or after the FORMAT and/or CIPHERED data.Likewise, the track data may be in any other order (e.g., TRACK3 datamay come before TRACK1 data). Further, the KSN or DSN data may belocated anywhere in the payload string.

In a particular example, the payload string may be formatted as:

-   FORMAT_CIPHERED_[TRACK1][_TRACK2][_TRACK3][_KSN][_DSN][_HWV_HARDWARE][_FMV_FIRMWARE]

As will be further discussed below, in particular embodiments, thesystem uses this payload string and the format of each data component tocreate a unique fingerprint for each device.

At step 436, the particular POI device is configured to transmit thepayload to a payment processing system. According to particularembodiments, the particular POI device is configured to transmit thepayload to a third party for payment processing. In at least oneembodiment, the system is configured to transmit the payload to apayment processing system associated with the P2PE Management System510. In some embodiments, the system is configured to transmit thepayload to any suitable intermediary for processing before being sent tothe payment processor. For the sake of brevity, this section of thisdocument refers to a payment processing system, which may mean any ofthe above.

The particular POI device may be configured to transmit the payload tothe payment processing system in any suitable way. According to someembodiments, the particular POI device is configured to transmit thepayload to the payment processing system via the internet. In one ormore embodiments, the particular POI device is configured to transmitthe payload to the payment processing system via a secure privatenetwork. In some embodiments, the particular POI device is configured totransmit the payload to the payment processing system via a LAN, WAN,Wi-Fi, hardline, or other suitable connection.

As will be understood from discussions herein, the particular POIdevice, in various embodiments is a “dumb” device. Thus, the particularPOI device, in these embodiments (and others) is configured to receivedata (whatever the data may be), encrypt the data based on the firmwareinstalled, compile and transmit the payload without regard to where thedata is headed, whether the POI device has been tamper with, whether thePOI device has been stolen, etc. It should also be understood that theparticular POI device may have a variety of other security measuresinstalled, such as, for example, tamper resistant casing, a circuitdesigned to self-destruct upon tampering, various audio or visualalarms, etc.

Exemplary P2PE Report Process (FIG. 4B)

Referring to FIG. 4A above, once a particular POI device (e.g., POIdevice 350), is received by a merchant and deployed, the particular POIdevice is, in various embodiments, ready to receive customertransactions. In these embodiments (and others), the merchant may berequired to produce one or more audit reports and attest to the state ofthe POI device (and any other POI devices in the merchant's possession).According to particular embodiments, the systems and methods herein areconfigured to gather information and product such audit reports.

Turning to FIG. 4B, the system, at step 431, is configured to receive arequest for an audit report from a computing device associated with amerchant. In various embodiments, the system is configured to receivethe request for the audit report from the computing device associatedwith the merchant by receiving log in information (e.g., which mayidentify the particular merchant) associated with a particular user(e.g., username, password, and/or other suitable credentials) andreceiving an indication that the particular user would like an auditreport. In one or more embodiments, the system is configured to receivethe request from the audit report from the computing device associatedwith the merchant by receiving the audit request from a particularcomputing device that is dedicated to communicating with the system(e.g., a computing terminal that is configured to only function with theP2PE Management System).

The audit report may be any suitable audit report that includes anysuitable information. In various embodiments, as discussed above, theaudit report may include information associated with one or more devicesassociated with the merchant and/or the status of each of the one ormore devices associated with the merchant. According to particularembodiments, the audit report includes an attestation of the informationassociated with each of the one or more devices associated with themerchant. In further embodiments, the audit report includes anattestation by the user (e.g., representing the merchant) that the userhas read, and/or that the merchant is in compliance with, a compliancemanual (e.g., a P2PE Instruction Manual or the like).

At step 433, the system is configured to, in response to receiving therequest for the audit report, retrieve merchant device informationassociated with the merchant. As discussed herein, in variousembodiments, the system is configured to receive information regardingthe chain of custody of various devices. In these embodiments (andothers), the system is configured to locate and retrieve informationregarding each device associated with the merchant. Such merchant deviceinformation may include any suitable information, including, but notlimited to: a device identifier, a device location, a device serialnumber, number of transactions processed by a device, a device status(e.g., “active”, “lost”, “tampered”, “stored”, etc.), etc.

According to particular embodiments, the audit report (e.g., requestedat step 431) may include an attestation to that the user (e.g.,representing the merchant) has read, and/or that the merchant is incompliance with, a compliance manual. In these embodiments (and others),the system is configured to retrieve a copy of the compliance manual todisplay to the user.

At step 435, the system is configured to display the merchant deviceinformation. In various embodiments, the system is configured to displaythe merchant device information including the merchant deviceidentifier, merchant device location, and merchant device status. Inparticular embodiments, the system is configured to display the copy ofthe compliance manual.

At step 437, the system is configured to request attestation of themerchant device information. In particular embodiments, the system isconfigured to request attestation by the user clicking one or more checkboxes. In various embodiments, the system is configured to requestattestation by the user typing or electronically signing their name. Infurther embodiments, the system is configured to request attestation bythe user entering in a code, filling out a document, clicking a button,scrolling to the end of a page or electronic document, etc.

At step 439, the system is configured to receive an indication ofattestation (e.g, the system is configured to receive an indication thatthe user has checked a box, filled out a form, signed an electronicform, etc.). At step 441, the system is configured to, in response toreceiving the indication of attestation, compile the audit report, theaudit report including the identifier of each device associated with themerchant, the status of each merchant device, and the indication ofattestation. The system may be configured to compile the audit report inany suitable way and the audit report may be in any suitable format.

At step 443, the system is configured to transmit the audit report tothe computing device associated with the merchant. The system may beconfigured to transmit the audit report to the computer deviceassociated with the merchant by displaying the audit report, accessingand causing the computing device associated with the merchant to printthe audit report, etc. In various embodiments, the system is configuredto transmit a copy of the attested to audit report to various otherentities, such as auditing entities, etc.

Exemplary Payment System Processes (FIG. 5A & FIG. 5B)

FIGS. 5A and 5B are exemplary processes performed by the P2PE ManagementSystem (e.g., P2PE Management System 510). FIG. 5A is an exemplarypayload integrity verification process and FIG. 5B is an exemplaryfingerprint creation process, which may be used as part of the payloadintegrity verification process.

Exemplary Payload Integrity Verification Process

Turning to FIG. 5A, the system, at step 530, is configured to receive apayload originating from a device, the payload including encryptedinformation and a device serial number. In various embodiments, thesystem is configured to receive the payload from a payment point ofinteraction device (e.g., a credit card swipe device). In particularembodiments, the system is configured to receive the payload from ahealth records computing device (e.g., a device that transmits sensitivehealth records for storage by the system). In further embodiments, thesystem is configured to receive the payload from a computing deviceassociated with financial information (e.g., bank account information,etc.). In still further embodiments, the system is configured to receivethe payload from any other suitable device, such as a devicetransmitting sensitive information such a driver's license number, asocial security number, etc.

The payload may include any suitable information (e.g., any suitablestring of particular elements). In various embodiments, the payloadincludes encrypted information and the device serial number. Inparticular embodiments, the payload includes a key serial number that isused to decrypt the encrypted information. In one or more embodiments,the payload includes a device firmware number. In further embodiments,the payload includes any other suitable device or payload informationassociated with the device, transaction, and/or merchant in custody ofthe device.

The encrypted information may be any suitable information that has beenencrypted, such as, for example, a social security number, a credit cardnumber, payment information, a driver's license number, medical recordinformation, a birthdate, a bank account number, a routing number, aname, etc. As discussed herein, the payload may be in any suitableformat, which may be used as a fingerprint for device identification.

At step 532, the system is configured to parse the payload to extractthe device serial number. In various embodiments, the system isconfigured to parse the payload to extract the device serial number byseparating the encrypted information from the unencrypted informationand determining which one or more unencrypted numbers are included inthe device serial number. In particular embodiments, the payloadincludes a string of numbers and information and the device serialnumber is located in a particular location of the string (e.g., thedevice serial number may be the first number, the second number, thefifth number, etc.). As will be understood by one of ordinary skill inthe art, the method of parsing the payload my depend upon thestructure/format of the payload.

At step 534, the system is configured to retrieve a serial number tablefrom the database, the serial number table including one or more serialnumbers. At step 536, the system is configured to compare the deviceserial number to the serial number table to determine whether the deviceserial number is included in the serial number table. The system may beconfigured to compare the device serial number to the serial numbertable in any suitable way including searching for the device serialnumber, comparing the device serial number to all serial numbers in thetable, and/or by using some other indicator (first number, etc.) tonarrow down the one or more serial numbers included in the serial numbertable that may match the device serial number. It should be understoodby one of ordinary skill in the art that the serial number table may bemore than one suitable serial number table.

At step 538, the system is configured to, upon determining that thedevice serial number is included in the table, retrieve, from memory, afingerprint associated with the device, wherein the fingerprint is anidentifier for the device based on the format of one or more payloadsthat originated from the device (see FIG. 5B regarding discussion offingerprint creation). In particular embodiments, the system isconfigured to create the fingerprint associated with the device, asfurther discussed herein. In further embodiments, the system isconfigured to receive the fingerprint associated with the device fromthird party system (e.g., a third-party system creates the fingerprintand transmits the fingerprint to the system. In still furtherembodiments, the device fingerprint is manually entered by one or moreusers.

At step 540, the system is configured to compare the payload to thefingerprint to determine whether the device has been compromised. Invarious embodiments, the system is configured to compare the format ofthe payload (e.g., the order of the particular elements of the payload)to the fingerprint (e.g., a representation of the format of a firstpayload receive from the device) to verify the format matches thefingerprint. In some embodiments, the system is configured to comparevarious elements of the payload to the format, such as the key serialnumber, the device firmware number, etc. to the fingerprint to determinewhether the device has been compromised (e.g., the if the comparedelement does not match the corresponding portion of the fingerprint, thedevice may have been compromised).

At step 542, the system is configured to, upon determining that thedevice has not been compromised, facilitating decryption of theencrypted information. In various embodiments, the system is configuredto facilitate decryption of the encrypted information by transmittingthe encrypted information (and/or the entire payload) to an HSM fordecryption. Upon determining that the device has been compromised, themay be configured to discard the payload, (e.g., not facilitatedecryption of the encrypted information), notify the merchant, change astatus of the device (e.g., as discussed herein), and/or no longeraccept payloads from the device.

Exemplary Payload Fingerprint Process

Generally, FIG. 5B shows an exemplary process for generating a devicefingerprint. Beginning with FIG. 5B, the system, at step 531, isconfigured to receive a payload from a device. The system may beconfigured to receive the payload from any suitable device, such as, forexample, any suitable device discussed above regarding step 530.

At step 533, the system is configured to determine whether the receivedpayload is the first payload received from the device. In variousembodiments, the system is configured to determine whether the receivedpayload is the first payload received from the device by comparing aserial number included in the received payload to a list of serialnumbers of devices from which payloads have been received. In one ormore embodiments, the system is configured to determine whether thereceived payload is the first payload received from the device bycomparing a device identifier received from a user-interface (e.g., auser inputs device serial numbers) to an identifier included in thedevice payload.

At step 535, the system is configured to, based on determining that thereceived payload is the first payload received from the device, parsethe received payload. The system may be configured to parse the devicepayload in any suitable way as discussed herein. At step 537, the systemis configured to determine the format of the payload. The system may beconfigured to determine the format of the payload in any suitable way.Further, the format of the payload may vary and may be in any suitableform as discussed herein, such as CHR, HEX, Base64, or any othersuitable format. In particular embodiments, the system may only storethe format of the payload but may not store track data.

For example, the payload format may be in the following format:

-   -   FORMAT_CIPHERED_[TRACK1][_TRACK2][_KSN][_DSN]

Continuing with the above example, “CIPHERED” is the encryptionalgorithm and may be, for example, RAW (data is unencrypted), TDES (DESDUKPT), or AES (AES DUKPT). Further, in this example, each TRACK isformatted at 1, 2, or 3, “+” and a CHR string “+” a string a numbers inHEX format, “+” a string of numbers in HEX format. Thus, in thisexample, TRACK1 above is formatted as 1+CHR+HEX+HEX. In this example,the fingerprint may be FORMAT is in HEX format, CIPHERED is TDES, TRACK1is in 1+CHR+HEX+HEX format, TRACK2 is in 2+CHR+HEX+HEX format, KSN (keyserial number) is in HEX format, and DSN (device serial number) is inHEX format. Therefore, the system may be configured to create afingerprint, in this example of:

-   -   HEX_TDES_1+CHR+HEX+HEX_2+CHR+HEX+HEX_HEX_HEX

At step 539, the system is configured to store in memory a fingerprintfor the device, the fingerprint based on the format of the receivedpayload. At step 541, the system is configured to compare eachsubsequent payload received from the device to device fingerprint (e.g.,to determine whether the device has been compromised). In variousembodiments, the system is configured to determine that the device hasbeen compromised when the format of a particular subsequent payload doesnot match the device fingerprint (e.g., someone has changed somethingabout the output of the device, such as the device firmware versionnumber, etc.).

Exemplary UML Diagrams

FIGS. 6-14 show UML diagrams illustrating various sequences of thepresent systems and methods. Particularly, FIGS. 6-14 depict exemplaryprocesses for point-to-point encryption (P2PE) transactions, whereinpayloads may include encrypted data, unencrypted data, or both. It willbe understood by one of ordinary skill in the art that these exemplaryprocesses may be used in any type of transaction, including, but notlimited to end to end encryption transactions. The lifelines and majorprocess components will be used throughout (e.g., QSAPI is representedby QSAPI 602 across FIGS. 6-14, wherever present).

In various embodiments, as shown in FIG. 6, a customer (e.g., merchant)posts data to be processed to a web application (e.g., via a webbrowser) at POST request 616. Based on the data included in the post,the web application chooses a script to run. Generally, FIGS. 6-14depict two script lifelines, qsapi-process-3.8.php 602 andvalidator.class.php 1320, which are further described below. As shown inFIGS. 6-14, the system uses at least two databases, a POI database(FIGS. 9 and 12) and a Quickswipe database (FIGS. 6, 8, 9, 10, 12, and14). In various embodiments, the POI database is a database that POIManager uses for persisting information on various devices. According toone or more embodiments, the Quickswipe database is a databaseoperatively connected to qsapi-process-3.8.php 602 and used to storevarious qsapi-process-3.8.php 602 information.

Exemplary Overall System Sequence

Turning to FIG. 6, the lifeline qsapi-process-3.8.php 602, in theembodiments shown, implements majority of the P2PE management systemfunctionality via a Quickswipe API (“QSAPI 602”). It should beunderstood by one of ordinary skill in the art that QSAPI 602functionality may be implemented by any suitable number of APIs,scripts, and/or functions. For simplicity and brevity, only QSAPI 602will be discussed. According to particular embodiments, and shown inFIG. 6, QSAPI 602 starts with instantiating specialized.PHP classes thatencapsulate different aspects of processing as described herein,including, but not limited to instances of Device, DevicesController andpoi classes.

Continuing with FIG. 6, “Device” class 610 is a base class for allsupported devices (e.g., POI devices, etc.). In particular embodiments,each type of device (e.g., each device brand, model, etc.) associatedwith the system has a corresponding child class inherited from theDevice class 610 (e.g., each brand of POI device has a separate childclass). In various embodiments, each child class includes one or moreaspects of a device's output inherited from the class, including, butnot limited to device payload format (e.g., XML or binary format), anindication of whether data is encrypted etc. According to particularembodiments, the Device class 610 receives information regarding eachtype of device via a fromString(device output) string, as shown in FIG.6, to instantiate the appropriate Device child class instance. Invarious embodiments, the Device class 610 uses the information in theappropriate child class to parse device payload (see fetch(deviceoutput)) for data decryption, if a device payload includes encrypteddata. In the embodiments shown in FIG. 6, the system uses Luna EFT HSMDevice 608 to decrypt device payload data.

In various embodiments, Device class 610 selects a child class to beinstantiated via a method fromString( ) (e.g., based on the device type,etc.), creates a new( ) instance, and calls a fetch( ) method. Accordingto particular embodiments, the fetch method parses device payload andstores parsed data. For example, Device class 610 method fromString( )returns a reference that contains the parsed data of a particularpayload. Continuing with this particular example, the fromStringreference may contain card track 1, 2, 3 data, a device serial number,and/or device firmware and hardware information (as discussed herein,the device payload data may include any suitable information).

Continuing with FIG. 6, DevicesController class 612 is a controllerclass that, in particular embodiments, encapsulates several activitiesthat QSAPI 602 uses to determine whether a particular device has beencompromised, tampered with, etc. In particular embodiments, aDevicesController class 612 instance is initialized with Quickswipedatabase 606 accessors. In various embodiments, DevicesController class612 transmits an indication of any such indication of device tamperingto the POI Manager (e.g., P2PE Management System, see FIG. 9), upondetection. According to one or more embodiments, DevicesController class612 retrieves and stores data at Quickswipe database 606 table entitleddevice_use.

An instance of poi class 614 is initialized by class_construct( )method. The construct method, according to particular embodiments,retrieves an HSM key index from the POI Manager (see FIG. 9) for legacydevices (e.g., one or more device payloads received by the system fromone or more devices that are not P2PE certified). As shown in FIGS.6-14, example poi processes are logIncident( ) and getHsmKey( ).Generally, in various embodiments, poi class 614 posts requests to POIManager and interprets POI Manager responses (see FIG. 9).

As shown in FIG. 6, Luna EFT HSM Device 608 (e.g., HSM Device 608), invarious embodiments, is specialized hardware to encrypt or decrypt data.As discussed herein, according to particular embodiments, a particulardevice is injected with a key at a Key Injection Facility. In theseembodiments (and others), this base key is stored in an HSM Device(e.g., HSM Device 608) in an internal table. Continuing with thisembodiment, in order to decrypt encrypted data from the particulardevice payload, a decrypt( ) method passes a key index included in theparticular device payload to the HSM Device 608 to derive the associatedtransaction key. In some embodiments, POI Manager stores HSM key indexesin POI database (as shown in FIG. 9) and QSAPI 602 retrieves variousbase keys by device serial number.

In various embodiments, once the Device class 610 inherited child classfor a particular device is received, QSAPI 602 determines which one ormore sub-processes (which “opt”) to complete (e.g., sub-processes 620,630, and 640). At step 620, if QSAPI 602 determines that the particulardevice payload does not contain a device serial number, QSAPI 602processes the particular Device as non-P2PE device (e.g., accordingly,in these embodiments (and others), QSAPI 602 does not retrieve orrequest the POI Manager's access key from the Quickswipe database).

Continuing with step 630, if QSAPI 602 determines that the particulardevice payload includes a device serial number, QSAPI 602 compares thedevice payload with a fingerprint associated with the device (asdiscussed herein) at “Capture Device,” which is further discussed atFIG. 8. In one or more embodiments, upon completion of the CaptureDevice process, QSAPI 602 receives a record of a device_use table inQuickswipe database 606.

At step 630, if QSAPI 602 determines that the particular device payloadincludes encrypted data, QSAPI 602 retrieves an HSM key index from POIManager to pass to HSM Device 608 for decryption as further described inFIG. 11 (Get HSM Key Index). If the Get HSM Key Index process returns anon-positive value, QSAPI 602 will terminate with sending an errorresponse. Otherwise Get HSM Key Index returns an HSM key index for usein decrypting any encrypted data included in the payload of theparticular device. See FIG. 12 for details on the Update Key Indexprocess.

According to particular embodiments, upon completion of the Update KeyIndex process (e.g., at FIG. 12), QSAPI 602 returns a decrypt(key index)method, which is passed to Device class 610. In various embodiments,Device class 610 uses the key index provided by the decrypt(key index)method to transmit necessary data to the HSM Device 608 for decryptingthe encrypted data of the payload of the particular device. In one ormore embodiments, Device class 610 transmits a DECIPHER2 Luna EFTcommand (including the key index and cipher data) to HSM Device 608,which decrypts the encrypted payload data of the particular device. Infurther embodiments, once decrypted, the decrypted payload data istransmitted from the HSM Device 608 to Device class 610 and decryptedclear tracks data are parsed by parseDecryptedData( ) In theseembodiments (and others), relevant data, including, but not limited to,parsed card tracks, PAN data, an expiration date, a cvv number, cardholder data, etc. are included in a data container CardData as shown inFIG. 6.

At step 640, in some embodiments, upon determining that the particulardevice payload does not contain encrypted data, QSAPI 602 calls Deviceclass 608 method parseTracks( ) to get a data container (e.g., CardDatacontainer) filled with a parsed card number, an expiration date, cardholder data, etc. At step 650, QSAPI 602 validates the data included inthe CardData container, which is further discussed regarding FIG. 13. Atstep 660, QSAPI 602 processes any exceptions at a Handle Exceptionsprocess, which is further discussed regarding FIG. 14.

Exemplary Capture Device Sequence

Turning to FIG. 8, the exemplary capture device process discussed hereinis implemented in embodiments where the payload of the particular deviceincludes the device serial number. QSAPI 602 calls Device class 608 fora string that identifies certain features of the payload of theparticular device (e.g., a device fingerprint as discussed herein andexemplary process shown in FIG. 7), including, for example, devicepayload format (e.g., XML, hexadecimal string, etc.), an indication ofwhether a portion of the device payload is encrypted, number of tracksincluded, etc. After a device payload format is determined, in variousembodiments, QSAPI 602 calls DevicesController class 612 methodcaptureDevice( ) with a device serial number, a device fingerprint, anda flag that indicates whether a portion of the device payload isencrypted.

In one or more embodiments, DevicesController class 612 searches for arecord of the particular device in a device_use record table at theQuickswipe database 606 using the device serial number of the particulardevice (e.g., at CaptureDevice( ) above). Upon finding a record of theparticular device at the Quickswipe database 606, DevicesControllerclass 612, in particular embodiments, examines various aspects of thedevice_use information (e.g., stored in the Quickswipe database 606). Insome embodiments, DevicesController class 612 determines whether thesystem has marked the particular device as tampered (e.g., the systemhas changed the state of the particular device to tampered). In theseembodiments, the system is configured to determine that the particulardevice has been marked as tampered if the date_disabled column returns a“NOT NULL” value (e.g., indicating that the particular device is markedas tampered by the POI Manager). Upon receiving a value of NOT NULL fordate_disabled column, according to particular embodiments, thecaptureDevice( ) method returns a “FALSE” value to QSAPI 602. In furtherembodiments, upon receiving the “FALSE” value for the captureDevice( )method, the QSAPI 602 sends an error response to a user and terminatesexecution of the process (e.g., does not proceed with decryption of anyencrypted payload information received from the particular device).

In various embodiments, upon receiving a value other than NOT NULL forthe date_disabled column, the system determines whether the encryptionflag for the particular device matches an encryption indication storedat the Quickswipe database 606. In particular embodiments, the systemcompares the received encrypted flag (e.g., as received with the payloadat captureDevice( ) above) against the encryption flag stored for theparticular device at Quickswipe database 606. According to particularembodiments, QSAPI 602 considers a change of encrypted flag (output wasencrypted, but now data is not encrypted) for a particular device as anindication that the particular device is compromised or tampered andshould be disabled. In these embodiments, the captureDevice( ) methodreturns FALSE to the QSAPI 602, which sends an error response to theuser and terminates execution of the process. For more informationregarding disabling devices, see FIG. 9.

According to one or more embodiments, upon determining that the receivedencryption flag matches the stored encryption indication at theQuickswipe database 606, the system is configured to compare the devicepayload format with a stored fingerprint for the particular devicestored at the Quickswipe database 606. According to particularembodiments, QSAPI 602 considers a change in device fingerprint as atemporary failure (several intermittent factors can cause device payloadformat to be different, such as, for example, unreliable USB connectionof device to the personal computer may cause a change in device payloadformat), for more details regarding temporary failure, see FIG. 10. Infurther embodiments, in response to the system determining theparticular device payload format does not match the fingerprint,captureDevice( ) returns FALSE, which results in QSAPI 602 sending anerror response to the user and to terminating execution of the process.

If all above checks were evaluated to False, captureDevice( ) methodreturns a current value of DEVICE_USE row to QSAPI 602. Upon determiningthat the particular device ss used for the first time (device_use rowNOT FOUND), DevicesController class 612 inserts a new device_use rowwith a passed encrypted flag and a device fingerprint in the Quickswipedatabase 606.

Exemplary Disable Device Sequence

Turning to FIG. 9, according to various embodiments, POI Manager 910tracks the chain of custody of devices. According to variousembodiments, POI Manager 910 is implemented as collection of .PHPclasses responsible for several activities. In some embodiments, POIManager 910 returns an appropriate controller class, such as theDevicesController class 612 based on the type of request posted by QSAPI602. As shown in FIG. 9, POI Manager 910 receives an indication todisable decryption of a particular device (e.g., the particular devicediscussed in the embodiments above) because the payload of theparticular device is unencrypted (e.g., but should have been decrypted).In the embodiment shown in FIG. 9, the particular device will bedisabled in Quickswipe database 606 and disable_date will be set to thevalue of current date and time. POI Manager 910 changes the state of theparticular device to tampered in POI database 920.

Exemplary Increment Failed Count Sequence

Turning to FIG. 10, QSAPI 602, in various embodiments, tracks eachfailed encryption attempt for every device with a known serial number.According to particular embodiments, when a particular device'sinformation is captured for the first time, the system adds a new row todevice_use table with failed_count set to 0 and max_failed_count set toa hardcoded limit (5, 10, etc.). In one or more embodiments, each time apayload is received from the particular device, QSAPI 602 runs avalidation check. In further embodiments, QSAPI 602 increments thefailed_count value each time a validation check fails. In still furtherembodiments, if the failed_count reaches the max_failed_count hardcodedlimit (e.g., 2, 5, 7, 10, 20, etc.), the system disables the particulardevice (e.g., and no longer decrypts payloads received from theparticular device). In particular embodiments, the system may beconfigured to reset the failed_count value to 0 with each passedvalidation check. In some embodiments, the system may be configured toincrement the failed_count value with each failed validation check,regardless of whether there has been an intermediate passed validationcheck. An exemplary disable device process is described above in regardsto FIG. 9.

Exemplary Get HSM Key Index Sequence

Upon determining that a particular device payload includes encrypteddata, QSAPI 602 follows the exemplary process shown in FIG. 11. Asdiscussed herein, in various embodiments, the particular device payloadincludes an integer value indicating a number of times a decryption keyvalue was derived from a base key. In some embodiments, HSM Device 608derives the encryption key from its internal copy of the base key anduses the derived encryption key to decrypt encrypted data in theparticular device payload.

According to particular embodiments, QSAPI 602 retrieves a poi_accessKeycorresponding to the particular device from poi class 614. In one ormore embodiments, upon determining that the poi_accessKey is NULL orempty, poi class 614 returns a legacy_key_index (e.g., indicating thatthe particular device is a “legacy device” and not part of a P2PEdecryption scheme). In various embodiments, upon determining that theparticular device serial number is not empty and poi_accessKey is notNULL, poi class 614 requests an hsm_key_id from POI Manager Web Server1110, as shown in FIG. 11.

As will be understood by one of ordinary skill in the art, in someembodiments, the HSM Device 608 stores more than one base key in aninternal HSM Device table. Thus, in these embodiments (and otherembodiments), the HSM Device 608 requires an indication of which of themore than one base key to use to decrypt the particular device payload.As described above, in some embodiments, POI Manager stores HSM keyindexes in POI database (as shown in FIG. 9) and QSAPI 602 retrievesvarious base keys by device serial number and transmits the HSM keyindex (which indicates the base key to use to decrypt the particulardevice payload) to the HSM Device 608.

Exemplary Update Key Index Sequence

FIG. 12 shows an exemplary update key index sequence. As shown in theembodiment in FIG. 12, if the system determines that the key indexassociated with a particular device has changed, then the system isconfigured to disable the particular device, as discussed above.

Exemplary Validation Sequence

Turning to FIG. 13, in the embodiment shown, upon receiving a payloadfrom a particular device, QSAPI 602 determines whether the payloadincludes track1 data in a correct format, track2 data in a correctformat, or both (e.g., by checking the fingerprint associated with theparticular device and/or other appropriate record). If the payload doesnot include track1 data in the correct format, track2 data in thecorrect format, or both, QSAPI 602 sends an error response to a user andterminates execution of the process. Continuing with this sequence, ifthe system determines the payload includes track1 data in the correctformat, track2 data in the correct format, or both (or any suitablenumber of tracks), in particular embodiments, QSAPI 602 proceedsvalidating track1, track2 or both. According to particular embodiments,card track data shall be non-empty string of numbers 0-9, which passmod10 check at validator.class.php 1320. In one or more embodiments, thesystem is configured to, upon successful validated card of the cardtrack number, DevicesController class 612 resets device_use.failed_count(as discussed above) for the particular device to zero (0).

Further Exemplary Processes

FIGS. 15-17 depict further exemplary processes of the systems discussedherein. In particular, FIG. 15 depicts an exemplary queuing process,FIG. 16 depicts an exemplary update process, and FIG. 17 depicts anexemplary decryption verification process. Each of these exemplaryprocesses will be discussed below.

Exemplary Queuing Process

Turning now to FIG. 15, an exemplary queuing process is depicted. Asfurther discussed herein, the system may be configured to queue variousmessages at a queue (e.g., MQTT Queues 231). In particular embodiments,the system may queue messages as a backup method in case a primary formof storage becomes unavailable. For example, in the example shown inFIG. 2B, should the Read/Write Database 232 stop functioning correctly,then queues hosted on the same machine as the Master Read-Only Database230 may preserve messages sent from the Master Read-Only Database 230 tothe Read/Write Database 232 until the Read/Write Database 232 isfunctioning or at least accepting and storing messages.

At step 1502, the system generates a message. As discussed herein, themessage may be any suitable message generated by any suitable componentof the system. In various embodiments, a frontend server (e.g.,Authentication Web Server 224) may generate a log or other suitableevent each time a payload is received and/or authenticated (as discussedherein). In particular embodiments, the frontend server may generate oneor more exceptions that are to be written to a database (e.g., anexception recording that a particular payload has failed authentication,etc.). In at least one embodiment, other components of the system maygenerate a message to be queued, such as, for example, a masterread-only database (e.g., Master Read-Only Database 230), a read-onlydatabase (e.g., Read-Only Database 228), or any other server orcomponent discussed herein.

At step 1504, the system adds the message to the queue. In particularembodiments, the system includes a queue that is hosted on the samecomputing device that hosts the Master Read-Only Database 230 (FIG. 2).In these embodiments, still referring to FIG. 2, the system isconfigured to add messages being sent from the Authentication Web Server224 to the queue.

At step 1506, the system stores the message at the queue. The system maybe configured to store the message at the queue for any predeterminedamount of time, until a particular event occurs, and/or until aparticular set of circumstances are met. In a particular embodiment, thesystem is configured to store the message at the queue for a number ofseconds, a number of minutes, a number of hours, for a particular numberof days (e.g., until a weekend or particular weekday), etc. In someembodiments, the system is configured to store the message at the queueuntil the system is processing less than 250 (or, e.g., 500, 750, 1,000,etc.) payloads per second, then the queue may be configured to transmitthe message. In further embodiments, the system may be configured tostore the message until a particular amount of resources are availableor until the intended recipient of the message (e.g., the Read/WriteDatabase 232) can accept the message (e.g., is functioning, is notmalfunctioning, is online, etc.).

At step 1508, the system determines whether a message recipient isconfigured to accept messages. At step 1510, the system, upondetermining that the message recipient is configured to accept messages,transmits the stored messages to the message recipient (e.g., aread/write database). Upon determining that the message recipient is notconfigured to accept messages, the system is configured to continueadding messages to the queue, but to not transmit any stored messages tothe message recipient.

Exemplary Update Process

FIG. 16 depicts an exemplary process for event-driven updates accordingto one embodiment of the present systems and methods. In variousembodiments, the system is configured to update various databases of thesystem upon a particular event occurring, such as, for example,receiving a piece of information. In at least one embodiment, the systemis configured to update various databases (e.g., the Master Read-OnlyDatabase 230) upon receiving information regarding a new device (e.g.,information regarding a new POI device received at the P2PE Manager 166as described in relation to FIG. 1).

At step 1602, the system generates or receives event information. Asfurther discussed herein, the system may generate or receive any eventinformation. In particular embodiments, the system may receive (orgenerate) event information related to new devices registered with thesystem (e.g., as discussed herein), event information related to statechanges of a particular device (e.g., a particular device's status ischanged from “active” to “tampered”), event information related to aparticular device that failed decryption, etc.

At step 1604, the system transmits new authentication data based on theevent information. In particular embodiments, the system is configuredto generate authentication data from the event information fortransmitting to one or more databases of the system for authenticationand validation of payloads transmitted to the system. At step 1606, thesystem refreshes a master database to include the new authenticationdata. At step 1608, the system refreshes one or more slave databases toinclude new authentication data. As a particular example, the systemreceives event information that a new device is registered with thesystem. In this particular example, the event information includes aserial number (or other suitable identifier) associated with the device.The system, continuing with this particular example, formats orotherwise generates authentication information associated with thedevice to be transmitted to databases of the system. In this way, inthis particular example, once the authentication data is transmitted tothe databases of the system (e.g., to the Read-Only Database 228), thesystem can use this authentication information to authenticate payloadsreceived from the device.

Exemplary Decryption Verification Process

Once a payload has been transmitted to, and processed by, a hardwaresecurity module, the system, in at least one particular embodiment, maybe configured to verify that the payload was decrypted. An exemplaryprocess for verifying decryption of a payload is shown in FIG. 17.Beginning at step 1702, a decryption server receives a payload thatincludes at least one encrypted element. In various embodiments, thedecryption server is configured to receive the payload from any suitablesource, including, but not limited to, a frontend server (e.g.,Authentication Web Server 224), a load balancer, a read/write database,directly from a third party partner (e.g., payment processor, healthcaresystem, government system, etc.), etc.

At step 1704, the decryption server transmits the payload to a hardwaresecurity module for decryption of the at least one encrypted element. Atstep 1706, the decryption server receives the payload from the hardwaresecurity module (e.g., after the hardware security module decrypts orattempts to decrypt the at least one encrypted element of the payload).

At step 1708, the decryption server parses the payload to locate the atleast one encrypted element. The system may be configured to parse thepayload in any suitable way, such as by locating the at least oneencrypted element based on the encrypted element's location within astring of text/code. At step 1710, the decryption server determineswhether the hardware security module decrypted the at least oneencrypted element. In various embodiments, the system is configured todetermine whether the hardware security module decrypted the at leastone encrypted element by comparing characters of the at least oneencrypted element to a database of characters. In particularembodiments, the system is configured to determine whether the hardwaresecurity module decrypted the at least one encrypted element bycomparing the number of characters of the at least one encrypted element(e.g., upon determining that the at least one encrypted element includesgreater than, less than, or a certain number of characters, the systemdetermines that the at least one encrypted element has been decrypted orhas not been decrypted). In further embodiments, the system isconfigured to determine whether the hardware security module decryptedthe at least one encrypted element by determining whether a payment cardnumber is included in the payload (e.g., a credit card number or otherpayment information).

At step 1712, upon determining that the hardware security module did notdecrypt the at least one encrypted element, the decryption servergenerates an error (e.g., which, in some embodiments, is transmitted toa read/write database and/or the third party partner) and may, in someembodiments, not transmit the payload to the third party partner. Atstep 1714, upon determining that the hardware security did decrypt theat least one encrypted element, the decryption server transmits thepayload to the third party partner.

CONCLUSION

Aspects, features, and benefits of the claimed invention(s) will becomeapparent from the information disclosed in the exhibits and the otherapplications as incorporated by reference. Variations and modificationsto the disclosed systems and methods may be effected without departingfrom the spirit and scope of the novel concepts of the disclosure.

It will, nevertheless, be understood that no limitation of the scope ofthe disclosure is intended by the information disclosed in the exhibitsor the applications incorporated by reference; any alterations andfurther modifications of the described or illustrated embodiments, andany further applications of the principles of the disclosure asillustrated therein are contemplated as would normally occur to oneskilled in the art to which the disclosure relates.

The foregoing description of the exemplary embodiments has beenpresented only for the purposes of illustration and description and isnot intended to be exhaustive or to limit the inventions to the preciseforms disclosed. Many modifications and variations are possible in lightof the above teaching.

The embodiments were chosen and described in order to explain theprinciples of the inventions and their practical application so as toenable others skilled in the art to utilize the inventions and variousembodiments and with various modifications as are suited to theparticular use contemplated. Alternative embodiments will becomeapparent to those skilled in the art to which the present inventionspertain without departing from their spirit and scope. Accordingly, thescope of the present inventions is defined by the appended claims ratherthan the foregoing description and the exemplary embodiments describedtherein.

What is claimed is:
 1. A system for decrypting payloads, the systemcomprising a computer server comprising at least one processorconfigured for: receiving a payload originating from a point ofinteraction device and partner authentication information from apartner; authenticating the partner via the partner authenticationinformation; parsing the payload into a first set of one or moreportions including: a device serial number; a key sequence number; andat least one encrypted portion; transmitting the at least one encryptedportion of the first set to a decryption service, the decryption servicefor decrypting the at least one encrypted portion; receiving decryptedcredit card information derived from the at least one encrypted portionfrom the decryption service; parsing the decrypted credit cardinformation into a second set of one or more portions including: acredit card number; an expiration date; and a CVV code; andtransmitting, to the partner, at least the second set.
 2. The system ofclaim 1, wherein the at least one processor is further configured for:receiving a client identifier and/or a reference number from thepartner; caching the client identifier and/or the reference number; andtransmitting, to the partner, the client identifier and/or the referencenumber with the credit card number, the expiration date, and the CVVcode.
 3. The system of claim 1, wherein the first set comprises dataobjects.
 4. The system of claim 1, wherein the second set comprises dataobjects.
 5. The system of claim 1, wherein the partner authenticationinformation comprises a partner identifier and a partner key.
 6. Thesystem of claim 1, wherein the first set is encoded.
 7. The system ofclaim 6, wherein the first set is encoded in hexadecimal format.
 8. Thesystem of claim 6, wherein the first set is encoded in Unicode.
 9. Thesystem of claim 6, wherein the first set is encoded in binary codeddecimal.
 10. The system of claim 6, wherein the first set is encoded inbase64.
 11. The system of claim 1, wherein the point of interactiondevice is wireless.
 12. A method for decrypting payloads, the methodcomprising: receiving, at a server, a payload originating from a pointof interaction device and partner authentication information from apartner; authenticating the partner via the partner authenticationinformation; parsing the payload into a first set of one or moreportions including: a device serial number; a key sequence number; andat least one encrypted portion; transmitting the at least one encryptedportion of the first set to a decryption service, the decryption servicefor decrypting the at least one encrypted portion; receiving decryptedcredit card information derived from the at least one encrypted portionfrom the decryption service; parsing the decrypted credit cardinformation into a second set of one or more portions including: acredit card number; an expiration date; and a CVV code; andtransmitting, to the partner, the second set.
 13. The method of claim12, the method further comprising: receiving a client identifier and/ora reference number from the partner; caching the client identifierand/or the reference number; and transmitting, to the partner, theclient identifier and/or the reference number with the credit cardnumber, the expiration date, and the CVV code.
 14. The method of claim12, wherein the first set comprises data objects.
 15. The method ofclaim 12, wherein the second set comprises data objects.
 16. The methodof claim 12, wherein the partner authentication information comprises apartner identifier and a partner key.
 17. The method of claim 12,wherein the first set is encoded.
 18. The method of claim 17, whereinthe first set is encoded in hexadecimal format.
 19. The method of claim17, wherein the first set is encoded in Unicode.
 20. The method of claim17, wherein the first set is encoded in binary coded decimal.
 21. Themethod of claim 17, wherein the first set is encoded in base64.
 22. Themethod of claim 12, wherein the point of interaction device is wireless.